From: Petr Baudis <pasky@ucw.cz>
To: Alexander Beyn <malex-git@fatelectrons.org>
Cc: git@vger.kernel.org
Subject: cg-log -r?
Date: Mon, 2 May 2005 02:04:47 +0200 [thread overview]
Message-ID: <20050502000447.GF974@pasky.ji.cz> (raw)
In-Reply-To: <20050502000019.GA1644@fatelectrons.org>
Dear diary, on Mon, May 02, 2005 at 02:00:19AM CEST, I got a letter
where Alexander Beyn <malex-git@fatelectrons.org> told me that...
> I created it because I could never remember if cg-log or cg-diff requires
> the -r before the revs.
Actually, would you people hate me / Cogito / Richard Stallman if I
added -r to cg-log and cg-mkpatch, for the sake of consistency?
Extending cg-log to work on individual files would be then obvious.
P.S.: Yes, I'm back and hope to catch with the rest of you during tomorrow.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-05-01 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 0:00 [PATCH] Add --help to cogito 0.8 Alexander Beyn
2005-05-02 0:04 ` Petr Baudis [this message]
2005-05-02 0:16 ` cg-log -r? Alexander Beyn
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=20050502000447.GF974@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=malex-git@fatelectrons.org \
/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).