2011/12/21 Garrett Serack :
> So the consensus is to take snapshots, not import history.
> I'm really good with that.
Yes. Just maintain snapshots of packaged project + history of
CoApp-specific changes.
> (since it really means that anything
> we're dealing with is 1 fork = (1 snapshot of a fore
nchpad.net
Subject: Re: [Coapp-developers] Easy way to mirror SVN repo at GitHub
2011/12/21 Vincent Povirk :
>> Simply put, I think we need to achieve something like this:
>>
>> http://happygiraffe.net/blog/files/wordpress_vendor_branch.png
>
> Brilliant. That picture sum
2011/12/21 Vincent Povirk :
>> Simply put, I think we need to achieve something like this:
>>
>> http://happygiraffe.net/blog/files/wordpress_vendor_branch.png
>
> Brilliant. That picture sums up what I mean exactly.
Vincent,
Fantastico. We are clear then.
Garrett,
What is your opinion about al
> Simply put, I think we need to achieve something like this:
>
> http://happygiraffe.net/blog/files/wordpress_vendor_branch.png
Brilliant. That picture sums up what I mean exactly.
___
Mailing list: https://launchpad.net/~coapp-developers
Post to :
2011/12/20 Vincent Povirk :
>> How do I do it?
>
> I've explained this in my previous post, and you appear to have
> understood. If there's something still unclear, please let me know.
I was typing my reply while reading, so later on I got it clarified indeed.
>> Indeed. That's why we need to hos
Whoops, forgot to include the list just now. Sorry for the confusion.
> How do I do it?
I've explained this in my previous post, and you appear to have
understood. If there's something still unclear, please let me know.
>> (And I REALLY don't want to have to install
>> bzr or hg or perforce on m
2011/12/20 Andrew Fenn :
> Sorry, when I first responded to your email it was on my phone and I
> misinterpreted what you wrote to mean that you wished to turn git repos into
> subversion ones.
>
> Please ignore the question.
No problem. Thanks for explanation.
Cheers,
--
Mateusz Loskot, http://
2011/12/20 Vincent Povirk :
> I think we should make it a policy to never convert other projects'
> revision control to git, if they're not already git, because the extra
> software it requires packagers to learn, install, and use does not
> convey any extra benefits.
This point is either clear to
Sorry, when I first responded to your email it was on my phone and I
misinterpreted what you wrote to mean that you wished to turn git repos
into subversion ones.
Please ignore the question.
2011/12/20 Mateusz Łoskot
> 2011/12/20 Andrew Fenn :
> > Could you explain in more detail why you need s
2011/12/20 Andrew Fenn :
> Could you explain in more detail why you need subversion in this workflow?
I am not entirely sure I understand the question.
Is it why I need Subversion tool (which I actually do not need)
or why I need to deal with repositories hosted in Subversion at all?
p.s. I have
I think we should make it a policy to never convert other projects'
revision control to git, if they're not already git, because the extra
software it requires packagers to learn, install, and use does not
convey any extra benefits. (And I REALLY don't want to have to install
bzr or hg or perforce
Hi,
I frequently need to make a GitHub mirror of a project with source
code hosted in SVN,
for example on SF.net. This also applies to many projects I want to
package with CoApp.
I have been testing various workflows and none has proved to be simple and
robust until I found git-svn-mirror tool wr
12 matches
Mail list logo
