All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Segato <daniele.segato@gmail.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-tag man: when to use lightweight or annotated tags
Date: Mon, 29 Jul 2013 20:21:39 +0200	[thread overview]
Message-ID: <51F6B2B3.2070404@gmail.com> (raw)
In-Reply-To: <51F2E673.5020401@xiplink.com>

On 07/26/2013 11:13 PM, Marc Branchaud wrote:
> On 13-07-26 01:19 PM, Daniele Segato wrote:
>>
>> By the way which is your role in the community?
>> Don't want to be rude, I just don't know who I'm talking about :) the
>> documentation maintainer?
>
> I'm just a git user and (very) occasional contributor.
>
> There's not much structure to the git community.  Anyone who wants git to
> change can post a patch (or patch series) to this list.  The patch can touch
> any area of the code, and it's considered good manners to CC whoever last
> touched the part(s) of the code being patched.
>
> The patch is discussed and revised as needed, and eventually the patch
> thread's participants arrive at a consensus as to whether or not the patch
> should become a part of git.  If the patch is accepted the git maintainer
> (Junio C. Hamano) shepherds the patch through git's release process.  See
> this note:
> 	http://git-blame.blogspot.ca/p/a-note-from-maintainer.html
> for more about that and other aspects of the git development community.
>
> 		M.
>

Thanks.
That helps a bit in understanding how I fit into the ml!

Cheers,
Daniele Segato

  reply	other threads:[~2013-07-29 18:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 10:17 git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default) Daniele Segato
2013-07-24 20:34 ` Junio C Hamano
2013-07-25 13:45   ` [PATCH] git-tag man: when to use lightweight or annotated tags Daniele Segato
2013-07-25 14:47     ` Marc Branchaud
2013-07-26  8:44       ` Daniele Segato
2013-07-26  8:46         ` Daniele Segato
2013-07-26 14:51           ` Marc Branchaud
2013-07-26 17:19             ` Daniele Segato
2013-07-26 17:33               ` [PATCHv3] " Daniele Segato
2013-07-26 19:06                 ` Jeff King
2013-07-26 19:36                   ` Jonathan Nieder
2013-07-29 18:02                     ` Daniele Segato
2013-08-07 12:32                       ` Daniele Segato
2013-07-26 21:13                   ` Marc Branchaud
2013-07-29 15:04                     ` Junio C Hamano
2013-07-29 18:20                       ` Daniele Segato
2013-07-27 10:39                   ` Daniele Segato
2013-07-27 11:26                     ` Philip Oakley
2013-07-27 11:45                       ` Stefan Beller
2013-07-29 18:16                         ` Daniele Segato
2013-07-26 21:13               ` [PATCH] " Marc Branchaud
2013-07-29 18:21                 ` Daniele Segato [this message]
2013-07-25 13:48   ` git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default) Daniele Segato

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51F6B2B3.2070404@gmail.com \
    --to=daniele.segato@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=marcnarc@xiplink.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.