Rumor goes that this is very difficult to do with Darcs. Is this correct?
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
2009/4/1 Peter Verswyvelen :
> Rumor goes that this is very difficult to do with Darcs. Is this correct?
I've always found it straightforward. Perhaps you should read the
manual http://darcs.net/manual/node8.html#SECTION0089
and try it out for yourself.
--
gwern
_
bugfact:
> Rumor goes that this is very difficult to do with Darcs. Is this correct?
darcs unpull
-- Don
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Don Stewart writes:
>> Rumor goes that this is very difficult to do with Darcs. Is this correct?
> darcs unpull
Or just cd to a different directory, and darcs get -t ?
-k
--
If I haven't seen further, it is by standing in the footprints of giants
_
Okay, thanks. So the rumors about this must be incorrect?
On Wed, Apr 1, 2009 at 9:57 PM, Ketil Malde wrote:
> Don Stewart writes:
>
> >> Rumor goes that this is very difficult to do with Darcs. Is this
> correct?
>
> > darcs unpull
>
> Or just cd to a different directory, and darcs get -t ?
Yes. It would be fairly easy to check this in the docs, too :)
bugfact:
> Okay, thanks. So the rumors about this must be incorrect?
>
> On Wed, Apr 1, 2009 at 9:57 PM, Ketil Malde wrote:
>
> Don Stewart writes:
>
> >> Rumor goes that this is very difficult to do with Darcs. Is this
>
Perhaps the rumours refer to non-tagged "versions"? In
conventional non-distributed version control systems, one
might go back to the version on a specific date, while with
darcs, that only makes sense wrt a specific repo (I think?).
So you can unpull all patches after a date from your local
rep
Oh I checked the docs. But I don't thrust the docs yet, I value the words of
the community higher. Since we're using Darcs to guard our hard work, I
thought I better double check :-)
I'm not really a newbie when it comes to source control actually. I wrote a
full blown version control system mysel
Yes, that might be the rumor indeed, it surely sounds like it :)
Darcs is really very different, so it takes a while to get used to it when
coming from other systems.
On Wed, Apr 1, 2009 at 11:25 PM, Claus Reinke wrote:
> Perhaps the rumours refer to non-tagged "versions"? In conventional
> non-d
Excerpts from Peter Verswyvelen's message of Wed Apr 01 23:39:15 +0200 2009:
[...]
> biggest problems I usually see in teams - namely forgetting to add files,
> forgetting to check in dependencies and the inability the merge after
> renames or moves -
Have a look at the --look-for-adds flag that
Peter Verswyvelen writes:
> Forgetting to add a file can be a nasty one, since if you discover
> that too late, the original file at patch time might not exist
> anymore (how do you guys solve this? Just plain discipline I
> guess?).
I've done this once, but with the cabal dependencies, not darc
Nicolas Pouillard writes:
> Excerpts from Peter Verswyvelen's message of Wed Apr 01 23:39:15 +0200 2009:
> [...]
>
>> biggest problems I usually see in teams - namely forgetting to add files,
>> forgetting to check in dependencies and the inability the merge after
>> renames or moves -
>
> Have a
On Wed, 1 Apr 2009, Don Stewart wrote:
bugfact:
Rumor goes that this is very difficult to do with Darcs. Is this correct?
darcs unpull
Be careful - you cannot revert this! If you want to unpull patches, that
were not distributed so far, you should better call 'darcs get' to get a
copy
On Wed, Apr 1, 2009 at 11:25 PM, Claus Reinke wrote:
> > Perhaps the rumours refer to non-tagged "versions"? In conventional
> > non-distributed version control systems, one
> > might go back to the version on a specific date, while with
> > darcs, that only makes sense wrt a specific repo (I think
14 matches
Mail list logo
