Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
To: Matt Rice <ratmice@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  gdb-patches@sourceware.org
Subject: Re: [RFA] Rename python files.
Date: Sat, 29 Aug 2009 16:59:00 -0000	[thread overview]
Message-ID: <200908291313.57162.thiago.bauermann@gmail.com> (raw)
In-Reply-To: <8ba6bed40908250828t8e6b44cv14af8402927da584@mail.gmail.com>

Em Terça-feira 25 Agosto 2009 12:28:17 Matt Rice escreveu:
> On Fri, Aug 14, 2009 at 12:11 AM, Eli Zaretskii<eliz@gnu.org> wrote:
> >> How should said renaming be done, by submitting and committing a patch
> >> which removes the old file and adds a new one, or by moving things
> >> around in CVSROOT?
> >
> > The latter is better, because it preserves the CVS history.  But I
> > think it requires special privileges on the repository.
>
> fyi I believe that by moving things around in the CVSROOT the changes
> will not be automatically picked by the cvs/git conversion.

I don't know much about conversions from CVS so I'll take your word on it. A 
quick search on the interwebs seem to indicate that conversion tools aren't 
good about detecting renames anyway, since CVS doesn't support the operation.

IMHO the best way to do it then is to use the CVS-friendly way of doing a 
"rename": cvs rm $FILE, cvs add $NEW_FILE. IUUC git would be able to detect 
such rename (though I don't know it would show up in an svn-converted repo).

Ok if I do it that way?
-- 
[]'s
Thiago Jung Bauermann


  reply	other threads:[~2009-08-29 16:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14  7:12 Thiago Jung Bauermann
2009-08-14 10:33 ` Eli Zaretskii
2009-08-25 15:29   ` Matt Rice
2009-08-29 16:59     ` Thiago Jung Bauermann [this message]
2009-08-29 18:01       ` Matt Rice
2009-08-25 17:11   ` Andreas Schwab
2009-09-03 22:27 ` Joel Brobecker
2009-09-07  0:48   ` Thiago Jung Bauermann
2009-09-07 21:43     ` Joel Brobecker
2009-09-09 17:47     ` Joel Brobecker

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=200908291313.57162.thiago.bauermann@gmail.com \
    --to=thiago.bauermann@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ratmice@gmail.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