From: "Agovic, Sanimir" <sanimir.agovic@intel.com>
To: 'Pedro Alves' <palves@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [COMMIT] Re: [PATCH 0/9][gdbserver] Split server.h.
Date: Fri, 06 Sep 2013 10:05:00 -0000 [thread overview]
Message-ID: <0377C58828D86C4588AEEC42FC3B85A7176797AB@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <5229A20A.5060302@redhat.com>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-owner@sourceware.org] On Behalf
> Of Pedro Alves
> Sent: Friday, September 06, 2013 11:36 AM
> To: Eli Zaretskii
> Cc: gdb-patches@sourceware.org
> Subject: Re: [COMMIT] Re: [PATCH 0/9][gdbserver] Split server.h.
>
> For some I-can't-justify reason, I've trained my brain to
> not expect to see new files in the "cvs diff" step.
> That "is a new entry, no comparison available" warning goes
> to stderr, but I failed to notice in the first patch. And
> then as I pushed the series in sequence, I skipped
> that 'cvs diff' step in between committing patches, so I ended
> up forgetting to add all new files...
>
> The simple fix for me without learning a whole new workflow
> seems to be to just use cvs diff -N. My ~/.cvsrc now has:
>
> diff -upN
>
> train myself to expect to see the new files in the
> resulting diff, and perhaps write a little wrapper script
> around cvs diff that warns me if there are non-added files
> in the resulting diff (the ? lines), unless there's already
> something like that in the set of cvs commands (cvs status
> seems to be practically useless, I never use it).
>
> Hopefully that'll help catch this mistake going forward.
>
Pedro, I use git-cvsexportcommit[1], it saves me from all the trouble.
[1] https://www.kernel.org/pub/software/scm/git/docs/git-cvsexportcommit.html
-Sanimir
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
next prev parent reply other threads:[~2013-09-06 10:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 20:26 Pedro Alves
2013-09-03 20:26 ` [PATCH 5/9] [gdbserver] Split a new ax.h file out of server.h Pedro Alves
2013-09-05 20:49 ` [PATCH 5/9] [gdbserver] Move bytecode compilation bits from server.h to ax.h. (was: Re: [PATCH 5/9] [gdbserver] Split a new ax.h file out of server.h.) Pedro Alves
2013-09-03 20:26 ` [PATCH 2/9] [gdbserver] Split a new remote-utils.h file out of server.h Pedro Alves
2013-09-03 20:26 ` [PATCH 8/9] [gdbserver] Split a new event-loop.h " Pedro Alves
2013-09-03 20:26 ` [PATCH 7/9] [gdbserver] Split a new dll.h " Pedro Alves
2013-09-05 20:50 ` Pedro Alves
2013-09-03 20:26 ` [PATCH 1/9] [gdbserver] Delete _ macro (gettext) Pedro Alves
2013-09-03 20:26 ` [PATCH 4/9] [gdbserver] Split a new tracepoint.h file out of server.h Pedro Alves
2013-09-03 20:26 ` [PATCH 9/9] [gdbserver] Split a new hostio.h " Pedro Alves
2013-09-05 20:50 ` Pedro Alves
2013-09-03 20:26 ` [PATCH 3/9] [gdbserver] Split a new utils.h " Pedro Alves
2013-09-03 20:54 ` [PATCH 6/9] [gdbserver] Split a new inferiors.h " Pedro Alves
2013-09-05 20:47 ` [COMMIT] Re: [PATCH 0/9][gdbserver] Split server.h Pedro Alves
2013-09-05 22:22 ` Pedro Alves
2013-09-05 23:52 ` Joel Brobecker
2013-09-06 5:47 ` Eli Zaretskii
2013-09-06 6:51 ` Ricard Wanderlof
2013-09-06 7:42 ` Eli Zaretskii
2013-09-06 9:36 ` Pedro Alves
2013-09-06 10:05 ` Agovic, Sanimir [this message]
2013-09-06 10:09 ` Pedro Alves
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=0377C58828D86C4588AEEC42FC3B85A7176797AB@IRSMSX105.ger.corp.intel.com \
--to=sanimir.agovic@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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