Re: stGIT: commit vs export vs mail

From: Catalin Marinas <catalin.marinas@gmail.com>
Date: Feb 17, 2006, 22:12 UTC
Message-ID: <43F64A51.10607@gmail.com>
In-Reply-To: <Pine.WNT.4.63.0602171139020.3052@jbrandeb-desk.amr.corp.intel.com>

Jesse Brandeburg wrote:

Show 13 quoted lines

> So I am using stgit .8 right now, and I'm having a hard time figuring
> out what the correct workflow should be for using stg and then
> committing a change
> 
> Here is what I've been doing:
> stg new test
>  enter my short description on first line
>  enter my long description on next lines.
> vi file
> stg refresh
> stg mail <blah blah blah>
> or
> stg commit

There is no "or" above but only "and maybe". The 'commit' command is only used to permanently store a set of patches into the repository. After that, you should not be able to change them anymore (well, someone just sent me a patch for an uncommit command). I only use this command when I work in the "maintainer" mode on StGIT. For contributing patches, you shouldn't need it since the base of the stack should usually be identical to the HEAD of the remote repository.

> Problem that I'm having right now is that the templates do the right
> thing for mail, but, the commit only puts in the "enter my..." text.

I don't fully understand this. Where does commit put the "enter my..." text?

> Is there a template based way to automatically append the author in the
> Signed-off-by: line when i do stg commit?

This can only be done when creating a patch. Commit doesn't modify the patches. I think you slightly misunderstood the commit command.

Catalin