Hi Simon,
On 12/08/2010 12:45 AM, Simon Peyton-Jones wrote:
> I have personal experience of git, because I co-author papers with git
> users. I am not very technologically savvy, but my failure rate with git
> is close to 100%. Ie I can do the equivalent of 'pull' or 'push' but I
> fail at everyt
On Wed, 8 Dec 2010, Stephen J. Turnbull wrote:
Ganesh Sittampalam writes:
> I think there are three things that can help with this problem:
>
> 1) a darcs rebase command. This will give you a nice way to manage the
> workflow already discussed, and you won't have to squish everything
> through
On Thu, 9 Dec 2010, Simon Marlow wrote:
On 08/12/2010 17:39, Yitzchak Gale wrote:
Some of those are already in the works, and all except possibly
(5) are known to be within reach. So the answer is yes, this
problem is now on the verge of being solved in Darcs.
I think that might be a little
Hi Simon,
Simon Peyton-Jones writes:
> | known problem with darcs with no obvious solution. For me, switching
> | GHC to git would certainly be a win.
>
> I have personal experience of git, because I co-author papers with git users.
> I am not very technologically savvy, but my failure rate wi
On 08/12/2010 17:39, Yitzchak Gale wrote:
Some of those are already in the works, and all except possibly
(5) are known to be within reach. So the answer is yes, this
problem is now on the verge of being solved in Darcs.
I think that might be a little overoptimistic. The fundamental problem
| thoroughly exhausted. Even when Darcs was in a far
| less advanced state than it is in now, the conclusion seemed
| to be that the best interests of the Haskell community at
| large are served by remaining with Darcs. So it would be a bit
| strange if this branching issue, which is a serious issu
Yitzchak Gale wrote:
> Iavor Diatchki wrote:
>> I use git for a lot of my development...
>> Given the responses though, it sounds like this is a well known
>> problem with darcs with no obvious solution.
>
> Why do you say there is no obvious solution? In fact, Ganesh,
> representing the Darcs tea
Iavor Diatchki wrote:
> I use git for a lot of my development...
> Given the responses though, it sounds like this is a well
> known problem with darcs with no obvious solution.
Why do you say there is no obvious solution? In fact, Ganesh,
representing the Darcs team, responded:
>> 1) a darcs reb
On Dec 8, 2010, at 2:45 AM, Simon Peyton-Jones wrote:
> If anyone has a favourite "how to understand git" doc, do point me at it.
You may have already tried these, but I've found the [official git tutorial][1]
to be pretty decent. The [second part][2] contains some details on how git sees
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/8/10 03:45 , Simon Peyton-Jones wrote:
> | known problem with darcs with no obvious solution. For me, switching
> | GHC to git would certainly be a win.
>
> I have personal experience of git, because I co-author papers with git users.
> I am n
On Wed, Dec 8, 2010 at 12:31 PM, Edward Z. Yang wrote:
> I like Git for Computer Scientists [1] and Git in pictures [2]. It also
> sounds like a Git for Darcs users might be in order.
Once you got the general ideas down I'd recommend
http://nvie.com/posts/a-successful-git-branching-model/
I like Git for Computer Scientists [1] and Git in pictures [2]. It also
sounds like a Git for Darcs users might be in order.
Edward
[1] http://eagain.net/articles/git-for-computer-scientists/
[2] http://blog.nelhage.com/2010/01/git-in-pictures/
___
Gl
| known problem with darcs with no obvious solution. For me, switching
| GHC to git would certainly be a win.
I have personal experience of git, because I co-author papers with git users. I
am not very technologically savvy, but my failure rate with git is close to
100%. Ie I can do the equiva
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/7/10 21:42 , David Peixotto wrote:
> P.S.
> Apparently Linus used to use Lennart's method of diff and patch for version
> control before switching to bitkeeper and then git:
> http://www.youtube.com/watch?v=4XpnKHJAok8 about 10:30 minutes in. I
It seems a shame that it would be so difficult to maintain a separate GHC
branch. Having no long-term branches myself, I haven't yet felt the pain, but
reading this email chain I am rather discouraged from attempting it.
It makes sense to me to have tool support for branching and merging in a l
Hello,
Thanks for all your responses (and the --skip-conflicts tip)! I use
git for a lot of my development, so I was hoping that I was just
experiencing "culture shock" and simply doing things with the wrong
mind-set. Given the responses though, it sounds like this is a well
known problem with d
On 06/12/2010 01:57, Iavor Diatchki wrote:
Hello,
I am doing some work on a GHC branch and I am having a lot of troubles
(and spending a lot of time) trying to keep my branch up to date with HEAD,
so I would be very grateful for any suggestions by fellow developers of how
I might improve the pro
Like everyone else I have no good solution.
When I had a ghc branch I used diff and patch to move my patches forward.
Not exactly what you expect to have to do with a version control system.
On Mon, Dec 6, 2010 at 1:57 AM, Iavor Diatchki wrote:
> Hello,
>
> I am doing some work on a GHC branch an
How could a darcs guy educate himself about this problem, by following your workflow and trying out some things ? Is
there an accessible developer's repo I could pull from to produce conflicts at a similar rate to you ? My usual repos
are not so conflictful.
__
On Mon, 6 Dec 2010, Simon Peyton-Jones wrote:
I too wish there was a good solution here. I've taken to making dated repos,
thus
http://darcs.haskell.org/ghc-new-co-17Nov10
When it becomes unusable, I make a brand new repo, with a new date
starting from HEAD, pull all the old patches
kell-users-boun...@haskell.org
[mailto:glasgow-haskell-users-
| boun...@haskell.org] On Behalf Of Iavor Diatchki
| Sent: 06 December 2010 01:57
| To: GHC Users Mailing List; darcs-us...@darcs.net
| Subject: How to develop on a (GHC) branch with darcs
|
| Hello,
|
| I am doing some work on
Hi,
On 6 December 2010 01:57, Iavor Diatchki wrote:
> I am doing some work on a GHC branch and I am having a lot of troubles
> (and spending a lot of time) trying to keep my branch up to date with HEAD,
> so I would be very grateful for any suggestions by fellow developers of how
> I might improv
Hello,
I am doing some work on a GHC branch and I am having a lot of troubles
(and spending a lot of time) trying to keep my branch up to date with HEAD,
so I would be very grateful for any suggestions by fellow developers of how
I might improve the process. Here is what I have tried so far:
Fir
23 matches
Mail list logo