[sage-devel] Re: mercurial --> plain text --> mercurial

Thanks Martin, I think the issue is that we want a version of our repository that has no binary data in it for transparency. The virus part is just a possible scenario that has been blown out of proportion because of the way I asked the question, since I didn't understand it well enough myself :)

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 10:11 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > That requires trusting Mercurial... ... > Again, this requires trusting Mercurial... If you don't trust your version control system, the whole exercise seems futile to me. Unless you're planning to actually read all the text durin

[sage-devel] Re: mercurial --> plain text --> mercurial

On Wed, Mar 26, 2008 at 3:21 PM, Mike Hansen <[EMAIL PROTECTED]> wrote: > > It seems like the mercurial mailing list would be the best place to go for > this. Done: http://selenic.com/pipermail/mercurial/2008-March/018133.html didier > > Using queues has made me quite a bit more productive,

[sage-devel] Re: mercurial --> plain text --> mercurial

William Stein wrote: > On Wed, Mar 26, 2008 at 1:18 PM, root <[EMAIL PROTECTED]> wrote: >> William, >> >> git can do this. Since git uses a hash it will always regenerate the >> same hash from the same file. >> >> In fact, git uses hashes all the way down the tree so you can just >> look at t

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 27, 6:11 am, "William Stein" <[EMAIL PROTECTED]> wrote: > On Wed, 26 Mar 2008 13:59:10 -0700, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > > On Mar 26, 2008, at 1:56 PM, mabshoff wrote: > > >> On Mar 26, 9:35 pm, Robert Bradshaw <[EMAIL PROTECTED]> > >> wrote: > > >>> I was talking abou

[sage-devel] Re: mercurial --> plain text --> mercurial

On Wed, 26 Mar 2008 13:59:10 -0700, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > On Mar 26, 2008, at 1:56 PM, mabshoff wrote: > >> On Mar 26, 9:35 pm, Robert Bradshaw <[EMAIL PROTECTED]> >> wrote: >> >>> I was talking about something more sophisticated than export/import, >>> which won't work t

[sage-devel] Re: mercurial --> plain text --> mercurial

Mike Hansen wrote: >> The queues feature in Mercurial is available independently in the >> quilt system. Mercurial makes this point: >> > > There are things with queues that you don't get with quilt. Quoting > from the book, > > "As an example, t

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 2008, at 1:56 PM, mabshoff wrote: > On Mar 26, 9:35 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: > >> I was talking about something more sophisticated than export/import, >> which won't work the instant one has multiple branches. One needs to >> actually create multiple heads, appl

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 9:35 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > I was talking about something more sophisticated than export/import,   > which won't work the instant one has multiple branches. One needs to   > actually create multiple heads, apply patches, then resolve them. Hg   > export doesn'

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 2008, at 1:30 PM, mabshoff wrote: > On Mar 26, 9:27 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: >> On Mar 26, 2008, at 11:53 AM, William Stein wrote: >> >> >> >>> Hi Jason (or anybody), >> >>> Does anybody have a clue if it is possible to take a directory >>> (e.g., >>> devel/sa

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 9:27 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > On Mar 26, 2008, at 11:53 AM, William Stein wrote: > > > > > Hi Jason (or anybody), > > > Does anybody have a clue if it is possible to take a directory (e.g., > > devel/sage/) with an .hg repo directory > > in it, and do the follo

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 2008, at 11:53 AM, William Stein wrote: > Hi Jason (or anybody), > > Does anybody have a clue if it is possible to take a directory (e.g., > devel/sage/) with an .hg repo directory > in it, and do the following: > > (1) export everything in the .hg repo to something (perhaps a ton of

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 11:53 am, "William Stein" <[EMAIL PROTECTED]> wrote: > Hi Jason (or anybody), > > Does anybody have a clue if it is possible to take a directory (e.g., > devel/sage/) with an .hg repo directory > in it, and do the following: > > (1) export everything in the .hg repo to something (perh

[sage-devel] Re: mercurial --> plain text --> mercurial

>> The queues feature in Mercurial is available independently in the >> quilt system. Mercurial makes this point: >> > >There are things with queues that you don't get with quilt. Quoting >from the book, > >"As an example, the integration of patche

[sage-devel] Re: mercurial --> plain text --> mercurial

> The queues feature in Mercurial is available independently in the > quilt system. Mercurial makes this point: > There are things with queues that you don't get with quilt. Quoting from the book, "As an example, the integration of patches with r

[sage-devel] Re: mercurial --> plain text --> mercurial

Mike, >Using queues has made me quite a bit more productive, and I'd like to >avoid switching to a version control system without them. Also, the >git documentation leaves something to be desired compared to the >Mercurial book. The queues feature in Mercurial is available independently in the

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 8:12 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Wed, Mar 26, 2008 at 1:18 PM, root <[EMAIL PROTECTED]> wrote: > > >  William, > > >  git can do this. Since git uses a hash it will always regenerate the > >  same hash from the same file. > > >  In fact, git uses hashes all the

[sage-devel] Re: mercurial --> plain text --> mercurial

It seems like the mercurial mailing list would be the best place to go for this. Using queues has made me quite a bit more productive, and I'd like to avoid switching to a version control system without them. Also, the git documentation leaves something to be desired compared to the Mercurial bo

[sage-devel] Re: mercurial --> plain text --> mercurial

On Wed, Mar 26, 2008 at 1:18 PM, root <[EMAIL PROTECTED]> wrote: > > William, > > git can do this. Since git uses a hash it will always regenerate the > same hash from the same file. > > In fact, git uses hashes all the way down the tree so you can just > look at the hash code of the root of

[sage-devel] Re: mercurial --> plain text --> mercurial

William, git can do this. Since git uses a hash it will always regenerate the same hash from the same file. In fact, git uses hashes all the way down the tree so you can just look at the hash code of the root of the tree to see if anything changes. Equal hash codes, even across the net, imply ex

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 7:53 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Hi Jason (or anybody), > > Does anybody have a clue if it is possible to take a directory (e.g., > devel/sage/) with an .hg repo directory > in it, and do the following: > >   (1) export everything in the .hg repo to something (per