From: Michele Ballabio <barra_cuda@katamail.com>
To: "Luís Sousa" <llsousa@ualg.pt>
Cc: git@vger.kernel.org
Subject: Re: Idea for git-touch
Date: Thu, 12 Nov 2009 18:18:01 +0100 [thread overview]
Message-ID: <200911121818.02502.barra_cuda@katamail.com> (raw)
In-Reply-To: <4AFC348B.4000202@ualg.pt>
On Thursday 12 November 2009, Luís Sousa wrote:
> I normally do commits when something works or on the end of the day,
> just to record what have doing. On other day, when I consider that is
> done/working I do a rebase -i squashing everything on one commit. The
> date of that commit will be preserved and is the date of the first
> commit. Then I do a git-reset HEAD~1, git-add . and git-commit with the
> same message to have the current date.
git rebase -i <...>
git rebase --ignore-date <...>
should do what you need.
prev parent reply other threads:[~2009-11-12 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 16:15 Idea for git-touch Luís Sousa
2009-11-12 17:01 ` Jan Krüger
2009-11-12 17:05 ` Luís Sousa
2009-11-12 17:08 ` Jan Krüger
2009-11-12 17:13 ` Luís Sousa
[not found] ` <4AFD26ED.4020602@op5.se>
2009-11-16 10:57 ` Luís Sousa
2009-11-12 17:18 ` Michele Ballabio [this message]
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=200911121818.02502.barra_cuda@katamail.com \
--to=barra_cuda@katamail.com \
--cc=git@vger.kernel.org \
--cc=llsousa@ualg.pt \
/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).