From: Simon Josefsson <simon@josefsson.org>
To: git@vger.kernel.org
Subject: Replacement for cvs2cl, for generating ChangeLog
Date: Tue, 27 Feb 2007 12:41:28 +0100 [thread overview]
Message-ID: <877iu3q13r.fsf@latte.josefsson.org> (raw)
Hi! I'm considering switching to git for my projects (shishi, gsasl,
gnutls, libtasn1, opencdk, ...) and I have some questions:
* How do I discard all locally modified or added files? 'cvs upd -C'
does some of that, but I've been using a tool 'cvsco' which quickly
restore a CVS checkout into a pristine state.
* Is there a tool that produce ChangeLog files in the GNU format,
based on the git logs? Similar to the 'cvs2cl' tool. The output
should look like:
2007-02-22 Simon Josefsson <simon@josefsson.org>
* link-warning.h, gl/getaddrinfo.c, gl/gnulib.mk, gl/string_.h,
gl/m4/gnulib-comp.m4, gl/m4/string_h.m4, lgl/Makefile.am,
lgl/snprintf.c, lgl/snprintf.h, lgl/stdio_.h, lgl/string_.h,
lgl/unistd_.h, lgl/m4/gnulib-comp.m4, lgl/m4/intdiv0.m4,
lgl/m4/snprintf.m4, lgl/m4/stdio_h.m4, lgl/m4/string_h.m4,
lgl/m4/unistd_h.m4: Update.
Thanks,
Simon
next reply other threads:[~2007-02-27 11:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 11:41 Simon Josefsson [this message]
2007-02-27 12:23 ` Replacement for cvs2cl, for generating ChangeLog Junio C Hamano
2007-02-27 12:37 ` Johannes Schindelin
2007-02-27 14:40 ` Sergey Vlasov
2007-02-28 14:08 ` gitco - replacement for cvsco Simon Josefsson
2007-02-28 19:55 ` Yann Dirson
2007-02-28 21:31 ` Simon Josefsson
2007-02-27 15:19 ` Replacement for cvs2cl, for generating ChangeLog Johannes Schindelin
2007-02-28 14:12 ` Simon Josefsson
2007-02-27 19:27 ` Junio C Hamano
2007-02-27 19:45 ` Johannes Schindelin
2007-02-27 20:54 ` Johannes Schindelin
2007-02-27 12:57 ` Andy Parkins
2007-02-27 15:56 ` Johannes Schindelin
2007-02-27 21:27 ` Robin Rosenberg
2007-02-27 21:50 ` Junio C Hamano
2007-02-27 22:22 ` Johannes Schindelin
2007-02-27 22:12 ` Johannes Schindelin
2007-02-28 14:27 ` Simon Josefsson
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=877iu3q13r.fsf@latte.josefsson.org \
--to=simon@josefsson.org \
--cc=git@vger.kernel.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).