git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Price <price@ksplice.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Geoffrey Thomas <geofft@mit.edu>,
	git@vger.kernel.org, Nanako Shiraishi <nanako3@lavabit.com>
Subject: Re: Unapplied patches reminder
Date: Sun, 6 Dec 2009 22:03:59 -0500	[thread overview]
Message-ID: <20091207030359.GK30538@dr-wily.mit.edu> (raw)
In-Reply-To: <7voco4gtxd.fsf@alter.siamese.dyndns.org>

Junio wrote:
> > From: Geoffrey Thomas <geofft@mit.edu>
> > Subject: [PATCH] diffcore-order: Default the order file to .git/info/order.
> > Date: Sat, 12 Sep 2009 19:49:48 -0400
> > Message-ID: <1252799388-16295-1-git-send-email-geofft@mit.edu>
> >
> >     Since order files tend to be useful for all operations in the
> >     project/repository, add a default location for the order file, so that
> >     you don't have to specify -O<orderfile> on every diff or similar
> >     operation.
>
> Except that "$GIT_DIR/info/order" is a bit too generic a name ("eh,
> 'order'?  Order of what?"), I do not think this will hurt, as no existing
> repositories would have such a file that would cause any behaviour change
> to existing users.  The reason I did not queue it was because there wasn't
> any discussion on it (not even the filename being too generic) which was
> an indication that not many people are interested in such a feature.
>
> That of course can be remedied by interested people speaking out.

I never use the -O option, but if this feature were available I think
I would use it.  It would make it possible to configure a helpful
order once -- for example, putting a changelog file first in order to
compare it with the commit message -- and then always use it without
effort.

A less generic name might be 'difforder'.

Greg

  reply	other threads:[~2009-12-07  3:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 20:20 Unapplied patches reminder Nanako Shiraishi
2009-10-18 23:31 ` Junio C Hamano
2009-10-18 23:31 ` Junio C Hamano
2009-10-19  8:10   ` Heiko Voigt
2009-10-18 23:31 ` Junio C Hamano
2009-10-19  6:49   ` Jeff King
2009-10-19  8:05     ` Junio C Hamano
2009-10-18 23:31 ` Junio C Hamano
2009-10-19 11:57   ` Rolf Bjarne Kvinge
2009-10-19 13:08   ` Per Strandh
2009-10-18 23:32 ` Junio C Hamano
2009-10-18 23:32 ` Junio C Hamano
2009-12-07  3:03   ` Greg Price [this message]
2009-10-18 23:32 ` Junio C Hamano
2009-10-18 23:32 ` Junio C Hamano

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=20091207030359.GK30538@dr-wily.mit.edu \
    --to=price@ksplice.com \
    --cc=geofft@mit.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nanako3@lavabit.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).