[Buildroot] buildroot-20070720

[Buildroot] buildroot-20070720

[Ulf Samuelsson]

Since the buildroot ftp site only maintains one month old tarball,
this package has already disappeared.
It would be good if that tarball could be downloadable as well
so that the diff can be computed.

-- 
Best Regards,
Ulf Samuelsson          mail:   ulf at atmel.com
Atmel Nordic AB
Box 2033, 174 52 Sundbyberg
Kavalleriv?gen 24, 174 58 Sundbyberg
Sweden
Tel:    +46 8 441 54 22 GSM:    +46 706 224457

[Buildroot] buildroot-20070720

[Bernhard Fischer]

On Tue, Aug 21, 2007 at 11:08:09PM +0200, Ulf Samuelsson wrote:
>Since the buildroot ftp site only maintains one month old tarball,
>this package has already disappeared.
>It would be good if that tarball could be downloadable as well
>so that the diff can be computed.

To me this doesn't make any sense at all.
svn co -r'{2007-07-20 00:00}' svn://uclibc.org/trunk/buildroot buildroot

What do you want to achieve with a tarball? Doesn't svn diff work just
fine? And, what's special about that 20070720 snapshot in the first
place?

[Buildroot] buildroot-20070720

[Ulf Samuelsson]

ons 2007-08-22 klockan 01:08 +0200 skrev Bernhard Fischer:
> On Tue, Aug 21, 2007 at 11:08:09PM +0200, Ulf Samuelsson wrote:
> >Since the buildroot ftp site only maintains one month old tarball,
> >this package has already disappeared.
> >It would be good if that tarball could be downloadable as well
> >so that the diff can be computed.
> 
> To me this doesn't make any sense at all.
> svn co -r'{2007-07-20 00:00}' svn://uclibc.org/trunk/buildroot buildroot
> 
> What do you want to achieve with a tarball? Doesn't svn diff work just
> fine? And, what's special about that 20070720 snapshot in the first
> place?

Sorry, wrong mailing list.
Was intended for an Atmel internal mailing list.
The "Evolution" Mail program does not easily show how
it completes a mail address.

http://www.atmel.no/buildroot/ is based on 20070718.
Would like to move this stuff to the main trunk

I got an earlier version in the summertime, and did not have
the original source so I diffed against the current,
and tried to figure out what was added.
That was the time, when I reverted some of your patches.

Would like to avoid that, so I want the original source.


-- 
Best Regards,
Ulf Samuelsson          mail:   ulf at atmel.com
Atmel Nordic AB
Box 2033, 174 52 Sundbyberg
Kavalleriv?gen 24, 174 58 Sundbyberg
Sweden
Tel:    +46 8 441 54 22 GSM:    +46 706 224457

[Buildroot] buildroot-20070720

[Ulf Samuelsson]

ons 2007-08-22 klockan 01:08 +0200 skrev Bernhard Fischer:
> On Tue, Aug 21, 2007 at 11:08:09PM +0200, Ulf Samuelsson wrote:
> >Since the buildroot ftp site only maintains one month old tarball,
> >this package has already disappeared.
> >It would be good if that tarball could be downloadable as well
> >so that the diff can be computed.
> 
> To me this doesn't make any sense at all.
> svn co -r'{2007-07-20 00:00}' svn://uclibc.org/trunk/buildroot buildroot
> 

OK, Early in the morning,so I did not see the "svn" statement
at the first scan.
This is exactly what I need, so Thank You.


> What do you want to achieve with a tarball? Doesn't svn diff work just
> fine? And, what's special about that 20070720 snapshot in the first
> place?
-- 
Best Regards,
Ulf Samuelsson          mail:   ulf at atmel.com
Atmel Nordic AB
Box 2033, 174 52 Sundbyberg
Kavalleriv?gen 24, 174 58 Sundbyberg
Sweden
Tel:    +46 8 441 54 22 GSM:    +46 706 224457

[Buildroot] buildroot-20070720

[Bernhard Fischer]

On Wed, Aug 22, 2007 at 05:47:57AM +0200, Ulf Samuelsson wrote:
>ons 2007-08-22 klockan 01:08 +0200 skrev Bernhard Fischer:
>> On Tue, Aug 21, 2007 at 11:08:09PM +0200, Ulf Samuelsson wrote:
>> >Since the buildroot ftp site only maintains one month old tarball,
>> >this package has already disappeared.
>> >It would be good if that tarball could be downloadable as well
>> >so that the diff can be computed.
>> 
>> To me this doesn't make any sense at all.
>> svn co -r'{2007-07-20 00:00}' svn://uclibc.org/trunk/buildroot buildroot
>> 
>> What do you want to achieve with a tarball? Doesn't svn diff work just
>> fine? And, what's special about that 20070720 snapshot in the first
>> place?
>
>Sorry, wrong mailing list.
>Was intended for an Atmel internal mailing list.
>The "Evolution" Mail program does not easily show how
>it completes a mail address.
>
>http://www.atmel.no/buildroot/ is based on 20070718.
>Would like to move this stuff to the main trunk
>
>I got an earlier version in the summertime, and did not have
>the original source so I diffed against the current,
>and tried to figure out what was added.
>That was the time, when I reverted some of your patches.
>
>Would like to avoid that, so I want the original source.

Perhaps it would be a good idea if you (atmel) would use an SCM instead
of tarballs. Would make your life way easier, i imagine. Just a
thought..

[Buildroot] buildroot-20070720

[Ulf Samuelsson]

----- Original Message ----- 
From: "Bernhard Fischer" <rep.dot.nop@gmail.com>
To: "Ulf Samuelsson" <ulf@atmel.com>
Cc: "Buildroot" <buildroot@uclibc.org>
Sent: Wednesday, August 22, 2007 10:08 AM
Subject: Re: [Buildroot] buildroot-20070720


> On Wed, Aug 22, 2007 at 05:47:57AM +0200, Ulf Samuelsson wrote:
>>ons 2007-08-22 klockan 01:08 +0200 skrev Bernhard Fischer:
>>> On Tue, Aug 21, 2007 at 11:08:09PM +0200, Ulf Samuelsson wrote:
>>> >Since the buildroot ftp site only maintains one month old tarball,
>>> >this package has already disappeared.
>>> >It would be good if that tarball could be downloadable as well
>>> >so that the diff can be computed.
>>> 
>>> To me this doesn't make any sense at all.
>>> svn co -r'{2007-07-20 00:00}' svn://uclibc.org/trunk/buildroot buildroot
>>> 
>>> What do you want to achieve with a tarball? Doesn't svn diff work just
>>> fine? And, what's special about that 20070720 snapshot in the first
>>> place?
>>
>>Sorry, wrong mailing list.
>>Was intended for an Atmel internal mailing list.
>>The "Evolution" Mail program does not easily show how
>>it completes a mail address.
>>
>>http://www.atmel.no/buildroot/ is based on 20070718.
>>Would like to move this stuff to the main trunk
>>
>>I got an earlier version in the summertime, and did not have
>>the original source so I diffed against the current,
>>and tried to figure out what was added.
>>That was the time, when I reverted some of your patches.
>>
>>Would like to avoid that, so I want the original source.
> 
> Perhaps it would be a good idea if you (atmel) would use an SCM instead
> of tarballs. Would make your life way easier, i imagine. Just a
> thought..
>

They are using "git" and remove all svn info before they enter into their git system.
They do not want to work with svn.

Is there any chance that buildroot is moving over to "git"?.

Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

[Buildroot] buildroot-20070720

[Bernhard Fischer]

On Wed, Aug 22, 2007 at 02:19:50PM +0200, Ulf Samuelsson wrote:
 
>> Perhaps it would be a good idea if you (atmel) would use an SCM instead
>> of tarballs. Would make your life way easier, i imagine. Just a
>> thought..
>>
>
>They are using "git" and remove all svn info before they enter into their git system.
>They do not want to work with svn.
>
>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 ;)

'nuff said. You folks probably know this much better than i do, or
something like that

friendly,
Bernhard

[Buildroot] buildroot-20070720

[Ulf Samuelsson]

>>
>>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

[Buildroot] buildroot-20070720

[Bernhard Fischer]

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?

Don't get me wrong, but this is really none of my business, currently.

Let me point you to the git documentation or google or the like

friendly,
Bernhard

[Buildroot] buildroot-20070720

[Benjamin Tietz]

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
>