From: Benjamin Tietz <benjamin@micronet24.de>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-20070720
Date: Wed, 22 Aug 2007 21:22:55 +0200 [thread overview]
Message-ID: <20070822192255.GA4736@firebird.dresden.micronet24.de> (raw)
In-Reply-To: <032a01c7e4e2$b5fb0fe0$980b7356@atmel.com>
On Wed, Aug 22, 2007 at 06:43:45PM +0200, Ulf Samuelsson wrote:
> >>
> >>Is there any chance that buildroot is moving over to "git"?.
> >
> > given that there is a svn backend for git, this doesn't make much sense
> > to me. They should just pull upstream, git should be able to take care
> > for (most of) the rest, but i'll not mandate how atmel does their
> > busyness here ;)
> >
>
> Personally, I have never used git except just cloning a tree.
>
> If I understand you correctly, I can pull stuff using git from the svn server
> and then add the stuff I get from my friends and do a merge
> and put back the end result using git talking to the svn server, right?
>
> Best Regards
> Ulf Samuelsson
Nearly. You can't do that with the native git tools.
There exist some tools, e.g. connecting your local git-repository to
some other type of repository. git-svn does that for svn.
git-svn init <SVN-URL>
will make your repo able to use svn. Afterwards do
git-svn fetch
to pull the svn-tree, and
git-svn commit
to push back the changes.
best regards
Benjamin
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2007-08-22 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 21:08 [Buildroot] buildroot-20070720 Ulf Samuelsson
2007-08-21 23:08 ` Bernhard Fischer
2007-08-22 3:47 ` Ulf Samuelsson
2007-08-22 8:08 ` Bernhard Fischer
2007-08-22 12:19 ` Ulf Samuelsson
2007-08-22 12:40 ` Bernhard Fischer
2007-08-22 16:43 ` Ulf Samuelsson
2007-08-22 19:19 ` Bernhard Fischer
2007-08-22 19:22 ` Benjamin Tietz [this message]
2007-08-22 4:35 ` Ulf Samuelsson
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=20070822192255.GA4736@firebird.dresden.micronet24.de \
--to=benjamin@micronet24.de \
--cc=buildroot@busybox.net \
/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