git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Knittl <knittl89@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Show branch information in short output of git status
Date: Sun, 23 May 2010 05:23:48 -0400	[thread overview]
Message-ID: <20100523092348.GA16811@coredump.intra.peff.net> (raw)
In-Reply-To: <AANLkTilkFHK1UIvSLEstXFIOJTsit02EZe1Wsoj_zRRX@mail.gmail.com>

On Fri, May 14, 2010 at 08:54:07AM +0200, Knittl wrote:

> > That being said, I still get "Initial commit on master". I think that
> > stat_tracking_branch just gives up if the branch doesn't exist (which
> > does make some sense). So in practice, I think your original and this
> > one actually behave the same (sorry, I know that changing it was my
> > suggestion).
> 
> yep, that's what i discovered too—but i don't care if this condition
> is 3 lines up or down. if stat_tracking_branch decides it will work
> for initial commits, then this code will do the expected thing

Agreed.

> should be no problem. the second patch changed quite a bit, so i
> thought it is easier to review when i send it as a separate patch. the
> final patch can be squashed of course

OK.  Nobody else seems to be commenting, so I would go ahead and put
together your final patch, cc-ing the maintainer.

> >  2. Your patch has wrapped lines which make it impossible to apply
> >     without fixing up manually. This is a common gmail problem.  See
> >     the "gmail" section of SubmittingPatches.
> 
> ok, browsed through that. i think i will just put my branch into a
> pasteservice or on a fileserver, unless the email way is *really*
> preferred—what about email attachments?

Inline email is best, but I think an email attachment would be preferred
to putting it on some out-of-band service (it's nice for the mailing
list archive to have a record of everything).

-Peff

  reply	other threads:[~2010-05-23  9:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02  9:13 [PATCH] Show branch information in short output of git status Knittl
2010-05-05  5:06 ` Jeff King
2010-05-06 12:24   ` Knittl
2010-05-07 16:05     ` Knittl
2010-05-12 13:35     ` Jeff King
2010-05-14  6:54       ` Knittl
2010-05-23  9:23         ` Jeff King [this message]
2010-05-25  7:19           ` Michael J Gruber
2010-05-25  7:22             ` Jeff King
2010-05-25  8:10               ` Michael J Gruber
2010-05-25  8:30               ` [PATCH] Documentation/SubmittingPatches: clarify GMail section and SMTP Michael J Gruber
2010-05-25  9:25                 ` Jeff King
2010-05-25  9:47                   ` Ævar Arnfjörð Bjarmason
  -- strict thread matches above, loose matches on Subject: below --
2010-05-02 10:10 [PATCH] Show branch information in short output of git status Knittl
     [not found] <AANLkTinNYcuiyRpgMGpQAEaStj2MDg9UooozooLPwv_0@mail.gmail.com>
2010-05-25 13:45 ` Michael J Gruber
2010-05-25 14:03   ` Michael J Gruber

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=20100523092348.GA16811@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=knittl89@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).