Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2016-02-04

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:06 mizu_no_oto joined #darcs
01:56 Riastradh joined #darcs
02:11 Big_G joined #darcs
02:50 pointfree joined #darcs
04:19 Heffalump joined #darcs
04:19 ggherdov` joined #darcs
04:19 peb` joined #darcs
04:20 JRHaigh joined #darcs
05:10 whaletechno joined #darcs
07:19 haasn joined #darcs
08:56 gh_ joined #darcs
09:19 gh_ Heffalump, we need a version bump in the topic
10:21 co-dan joined #darcs
12:57 ggherdov` joined #darcs
13:46 gal_bolle joined #darcs
14:03 PEB` joined #darcs
14:19 Big_G joined #darcs
15:54 Riastradh joined #darcs
17:19 gal_bolle joined #darcs
17:35 amgarching joined #darcs
18:20 Topic for #darcs is now http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.10.3 is out http://darcs.net/Releases/2.10
19:53 prsai joined #darcs
20:06 drewbug joined #darcs
20:09 drewbug > Let’s say you follow the development of an open-source project, and you have some controversial patches that aren’t accepted by the official maintainers. No problem – make your changes and publish your own repository. It’s a fork, of sorts, but it’s still connected to the mainline. Whenever the official project makes changes, you can do a darcs pull to get them, and resolve any conflicts. This way, your fork is kept up to date.
20:09 lambdabot <hint>:1:4: lexical error at character '\8217'
20:09 drewbug How does this work if the official project isn't using darcs?
20:15 prsai what system is using?
20:21 drewbug The occasional release of signed tarballs
20:24 prsai I would untar in a new repo, and cherry pick your changes from your modified repo to the new repo
20:25 prsai and hope there is not many conflicts
20:27 drewbug Okay, I'll give it a shot. Thanks!
20:31 prsai you're welcome
20:40 Heffalump I've done this myself in the past - keep a separate repo which I updated from mainline as "master", and pulled into my private one
20:41 Heffalump in the "master" repo I keep it just following upstream, and do a 'darcs record' whenever new changes come in
20:41 Heffalump in my own repo I just pull from master
20:47 sm drewbug: other vcses call this rebasing
20:48 sm you "rebase" your changes against the upstream trunk, periodically
20:49 sm darcs automates this, whenever it can
20:53 drewbug Would https://en.wikipedia.org/wiki/Quilt_(software) maybe be better for this use-case?
20:56 haasn joined #darcs
21:27 Heffalump I guess quilt is intended as a VCS agnostic way of doing that
21:28 Heffalump I think darcs is pretty good at managing the merging that you need for it (particularly when conflicts are uncommon)
21:28 Heffalump but I don't know which would have the smoothest workflow in your specific case
21:35 sm I think you can do this pretty efficiently with any vcs
21:35 sm darcs pull, git pull --rebase, and when it doesn't merge cleanly you do manual fixups - I think that's the least work you can expect
21:52 Heffalump with darcs it's easier to go back as well

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary