From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Collection of stgit issues and wishes
Date: Sun, 10 Dec 2006 22:26:44 +0000 [thread overview]
Message-ID: <b0943d9e0612101426l763d46cahe15683410cb4398d@mail.gmail.com> (raw)
In-Reply-To: <200612101801.58247.jnareb@gmail.com>
On 10/12/06, Jakub Narebski <jnareb@gmail.com> wrote:
> Catalin Marinas wrote:
> > On 10/12/06, Jakub Narebski <jnareb@gmail.com> wrote:
> >>>> Here are some issues which are a bit annoying for me:
> >>>> - make "stg help" (without command name) equivalent to "stg --help"
> >
> > There was a patch in this area. Doesn't it work correctly now?
>
> I use stgit 0.11
I was in general referring to the latest HEAD in the StGIT repository.
>
> 1056:[gitweb/web!git]$ stg help
> usage: stg help <command>
>
> while "stg --help" lists all commands.
Works correctly in the latest snapshot.
> >> And as far as I can see it doe not use git credentials (user.name and
> >> user.email).
> >
> > StGIT now uses the GIT credentials (and config files).
>
> Hmmm... in stgit 0.11 "stg refresh --sign" once gave me Signed-off-by:
> Nobody line instead of using git user.name and user.email.
Again, it is different in the latest snapshot (feature added post 0.11).
> The git commands StGit uses to perform operations automatically record
> changes in branches in reflog. What StGit does not provide is the "reason".
> You do use git-update-ref?
Yes, only for updating HEAD. The refs in refs/patches/<branch>/ are
written directly. I initialy wanted to add patch history support using
reflogs and added "git-update-ref -m ..." for the patch commits but I
found slow the pushing operation a bit. Do you only want to track the
reflogs for HEAD?
--
next prev parent reply other threads:[~2006-12-10 22:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 22:17 Collection of stgit issues and wishes Yann Dirson
2006-12-08 22:27 ` Jakub Narebski
2006-12-10 8:55 ` Jakub Narebski
2006-12-10 11:06 ` Jakub Narebski
[not found] ` <b0943d9e0612100831t7b79d4b1p436de5dbb813e51a@mail.gmail.com>
2006-12-10 17:01 ` Jakub Narebski
2006-12-10 22:26 ` Catalin Marinas [this message]
2006-12-10 23:02 ` Jakub Narebski
2006-12-10 23:24 ` Catalin Marinas
2006-12-10 23:37 ` Jakub Narebski
2006-12-11 12:59 ` Catalin Marinas
2006-12-21 11:39 ` Jakub Narebski
2006-12-11 18:41 ` Yann Dirson
2006-12-13 22:14 ` Catalin Marinas
2006-12-21 23:48 ` Jakub Narebski
2006-12-10 16:25 ` Catalin Marinas
2006-12-17 23:15 ` Yann Dirson
2006-12-12 9:43 ` Catalin Marinas
2006-12-12 10:02 ` Jakub Narebski
2006-12-13 7:22 ` David Kågedal
2006-12-13 10:20 ` Andreas Ericsson
2006-12-13 11:03 ` Karl Hasselström
2006-12-17 23:21 ` Yann Dirson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0943d9e0612101426l763d46cahe15683410cb4398d@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).