Skip to Content.
Sympa Menu

sm-commit - Re: [SM-Commit] GIT changes to master grimoire by Flavien Bridault (d699086195555f48071499d1c5695cc74aa48c50)

sm-commit AT lists.ibiblio.org

Subject: Source Mage code commit list

List archive

Chronological Thread  
  • From: Jaka Kranjc <lynx AT mages.ath.cx>
  • To: sm-commit AT lists.ibiblio.org
  • Subject: Re: [SM-Commit] GIT changes to master grimoire by Flavien Bridault (d699086195555f48071499d1c5695cc74aa48c50)
  • Date: Tue, 15 Aug 2006 19:19:56 +0200

> > New commits:
> > commit d699086195555f48071499d1c5695cc74aa48c50
> > Author: Flavien Bridault <vlaaad AT sourcemage.org>
> > Commit: Flavien Bridault <vlaaad AT sourcemage.org>
> >
> > HISTORY entry to explain the reason of the PATCHLEVEL++
> >
> > commit bfb2f7e4ae69209675059108736dedef467af893
> > Author: Flavien Bridault <vlaaad AT sourcemage.org>
> > Commit: Flavien Bridault <vlaaad AT sourcemage.org>
> >
> > and of course PATCHLEVEL++ so that people get it...
>
> If you have changes that belong together in your git clone, you can
> either use git-cherry-pick -n into a new branch to collect them into a
> single commit or use git reset HEAD^2 and then commit again as a single
> commit.
> This only works as long as it's not pushed yet, but it's nice in that
> case.
git commit --amend path/
is even quicker and easy to remember. Already in the guide.

Attachment: pgpmv4mQeNi5A.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page