Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Steinar Bang <sb@dod.no>
Cc: gdb@sourceware.org, binutils@sourceware.org
Subject: Re: A Proposal to Move to Git
Date: Tue, 27 Aug 2013 16:21:00 -0000	[thread overview]
Message-ID: <521CD380.8000002@gmail.com> (raw)
In-Reply-To: <upzc38pvcv1w.fsf@dod.no>

On 2013-8-27 18:00, Steinar Bang wrote:
>>>>>> NightStrike <nightstrike@gmail.com>:
> 
>> ... Git users can easily use git-svn, which means you can satisfy
>> mostly everyone, and still be using current, well maintained software.
> 
> git-svn is broken on the Win32 platform.  It can get you a git checkout
> with the full history.  The problems start when you wish to push your
> changes back into subversion.  Then you have to either do a merge or a
> rebase against the branch tracking the remote subversion repository, and
> you end up getting a conflict in all files you have changes in.
> 
> When I tried it, the conflicts with merge, were the entire files (which
> is pretty useless. With rebase and with merge using the
> ignore-space-change option, the conflicts were just my changed lines,
> but with CRLF/LF issues.
> 
> Ie. I got a conflict on all of my changes whether they were a conflict
> or not.
> 
> I tried switching off core.autocrlf in git and I tried convincing
> git-svn that the svn checkout shouldn't do CRLF/LF translation, but I
> had no luck with that.
> 
> My experiments were in msysgit 1.8.3-preview20130601.
> 
> (For the record: if someone have a procedure that can make this a
> non-issue I would be happy to be proved wrong)
> 
I'm using the same msysgit and TortoiseGit, I can use git-svn without such conflict issue.
I can successfully commit changes to Codeblocks' SVN repo
http://sourceforge.net/projects/codeblocks/ by git-svn.
My setting of local git is: auto crlf is true, safe crlf is false.

Yuanhui Zhang



  parent reply	other threads:[~2013-08-27 16:21 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 21:12 Tom Tromey
2013-08-20 21:16 ` Andrew Pinski
2013-08-20 21:26   ` Joseph S. Myers
2013-08-20 21:19 ` Joel Brobecker
2013-08-20 21:21 ` Paul_Koning
2013-08-20 22:59 ` Phil Muldoon
2013-08-21 15:05 ` Eli Zaretskii
2013-08-21 15:32   ` Andreas Schwab
2013-08-21 15:54     ` Eli Zaretskii
2013-08-26  8:05       ` Andreas Schwab
2013-08-21 18:40   ` Steinar Bang
2013-08-21 20:05     ` Eli Zaretskii
2013-08-21 20:38       ` Andreas Schwab
2013-08-22 18:56   ` Florian Weimer
2013-08-21 15:38 ` Steve Ellcey
2013-08-21 15:50   ` Joel Brobecker
2013-08-22  6:10     ` Tristan Gingold
2013-08-22 14:16   ` Richard Earnshaw
2013-08-22 14:25     ` Joel Brobecker
2013-08-22 14:39       ` Fred Cooke
2013-08-22 20:10 ` Mark Kettenis
2013-08-22 20:21   ` Fred Cooke
2013-08-22 20:22   ` David Miller
2013-08-22 20:48     ` Andrew Pinski
2013-08-22 21:07   ` Andreas Schwab
2013-08-22 21:10   ` Tom Tromey
2013-08-23 15:40     ` H.J. Lu
2013-08-23 15:55       ` Joel Brobecker
2013-08-23 16:03         ` Paul_Koning
2013-08-23 16:05           ` H.J. Lu
2013-08-26 12:37             ` NightStrike
     [not found]               ` <upzc38pvcv1w.fsf@dod.no>
2013-08-27 16:21                 ` asmwarrior [this message]
2013-08-23 16:03         ` H.J. Lu
2013-08-23 16:09           ` Joel Brobecker
2013-08-23 16:24       ` Matt Rice
2013-08-23 16:37         ` H.J. Lu
2013-08-23 16:47           ` Matt Rice
2013-08-23 17:01             ` H.J. Lu
     [not found]       ` <87siy070su.fsf@dod.no>
2013-08-24  0:27         ` Doug Evans
2013-08-22 23:55   ` Alan Modra
2013-08-30 22:58 ` Hans-Peter Nilsson
2013-08-30 23:37   ` Joseph S. Myers
2013-08-31  2:05     ` Hans-Peter Nilsson
2013-08-31 16:58       ` Joseph S. Myers
2013-09-04 16:55       ` Doug Evans

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=521CD380.8000002@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=sb@dod.no \
    /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