git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ulrich Gemkow <ulrich.gemkow@ikr.uni-stuttgart.de>, git@vger.kernel.org
Subject: Re: Trivial enhancement: All commands which require an author should accept --author
Date: Thu, 30 Aug 2018 13:51:38 +0200 (DST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1808301350340.71@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqpny1at28.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Wed, 29 Aug 2018, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > The `stash` command only incidentally requires that the author is set, as
> > it calls `git commit` internally (which records the author). As stashes
> > are intended to be local only, that author information was never meant to
> > be a vital part of the `stash`.
> >
> > I could imagine that an even better enhancement request would ask for `git
> > stash` to work even if `user.name` is not configured.
> 
> This would make a good bite-sized microproject, worth marking it as
> #leftoverbits unless somebody is already working on it ;-)

Right.

What is our currently-favored approach to this, again? Do we have a
favorite wiki page to list those, or do we have a bug tracker for such
mini-projects?

Once I know, I will add this, with enough information to get anybody
interested started.

Ciao,
Dscho

  reply	other threads:[~2018-08-30 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 21:05 Trivial enhancement: All commands which require an author should accept --author Ulrich Gemkow
2018-08-29 16:14 ` Johannes Schindelin
2018-08-29 19:09   ` Junio C Hamano
2018-08-30 11:51     ` Johannes Schindelin [this message]
2018-08-30 12:29       ` Ævar Arnfjörð Bjarmason
2018-08-30 14:08         ` Johannes Schindelin
2018-09-03 13:18           ` Ævar Arnfjörð Bjarmason
2018-08-30 14:26         ` Junio C Hamano
2018-09-04 17:18           ` Jonathan Nieder

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=nycvar.QRO.7.76.6.1808301350340.71@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ulrich.gemkow@ikr.uni-stuttgart.de \
    /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).