Santi BÃjar <santi@xxxxxxxxxxx> writes: > Signed-off-by: Santi BÃjar <santi@xxxxxxxxxxx> > --- > Hi *, > > just resend a patch that maybe was missed inside this thread: No, I didn't miss it. The new text says 'push "matching" branches' before explaining what it is, only vaguely refers the reader to the next section by "see below" without telling which part of below the reader should look at. In other words, it wastes two lines without adding two lines worth of additional information. Saying "look for string 'default' below" might be an improvement ;-), but then the reader can do that without being told to do so themselves, so... > Subject: possible bug when pushing with multiple remote repos. > From: Arnaud Mouiche > Date: 2010-10-22 9:12:51 > http://marc.info/?i=1287738771.13348.34.camel%20()%20amolinux > > Santi > > Documentation/git-push.txt | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt > index e11660a..9a2a93e 100644 > --- a/Documentation/git-push.txt > +++ b/Documentation/git-push.txt > @@ -23,6 +23,8 @@ You can make interesting things happen to a repository > every time you push into it, by setting up 'hooks' there. See > documentation for linkgit:git-receive-pack[1]. > > +The default operation mode if no explicit refspec is found is > +to push "matching" branches, see below. > > OPTIONS[[OPTIONS]] > ------------------ > -- > 1.7.3.2.337.gc40334 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html