unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/2] Tcsh update for core-updates
Date: Fri, 24 Feb 2017 17:28:35 +0000	[thread overview]
Message-ID: <20170224172835.ksfnvbcqw5rqprwa@wasp> (raw)
In-Reply-To: <20170224165511.GA28458@jasmine>

On 17-02-24 11:55:11, Leo Famulari wrote:
> On Fri, Feb 24, 2017 at 09:40:38AM +0000, ng0 wrote:
> > On 17-02-24 03:16:43, Leo Famulari wrote:
> > > This updates tcsh to the latest upstream version.
> > 
> > some weeks ago I worked on this. Put a significant amount of time into
> > the update, waited for replies and asked upstream about the cdhome
> > issue as I don't understand tcsh syntax that much.
> > This is exactly why I don't think email is the perfect tool for project
> > work. There is no reminder to tell you someone already worked on this,
> > no interactive search unless you have it yourself.
> > It would be good if you could search the archive next time and tell me
> > to rebase or redo it on core-updates.
> 
> I understand that is frustrating, but I did read that discussion before
> starting to work on my patch. Also, Tobias worked on it last August.

Okay, I didn't find Tobias work either*, so blame on me too. My initial
reaction was frustration though.
(* or did I? It's too long since I worked on tcsh)
There were no updates as I waited for someone more knowledgable in the
tcsh language than myself - either upstream (where I didn't get much
help) or within our community. None of that happened and the work I did
which wasn't updated was just synced to my git.

> In both cases, there were some questions about the changes, and then the
> patch authors stopped working on the patch. Now, tcsh is blocking
> core-updates, so I decided to try updating tcsh.

Okay, that's something I wasn't involved with so I didn't know. Thanks
for letting me know.

> It's hard to take a pre-existing patch from somebody else and try to
> figure out what parts are necessary, which parts can be discarded, which
> parts should be adjusted, et cetera. Especially for a complicated
> package update that requires adjusting patch files.
> 
> It's a lot easier to try the upgrade from scratch and fix problems as I
> find them.

I agree with this to some degree. Sometimes fixing the patch works, but
sometimes it just doesn't. I've encountered the case where it didn't
help anymore when I started working on git-shallow-clone by Andy from 2
years ago.


Anyway, no harm done, I just wanted to express what I felt.
What counts is that we don't start bulldozer'ing over each others work
and that the problem is fixed in the end.

Wether both Tobias and my work helped you or not, Thanks for fixing the
long overdue tcsh update :)

      reply	other threads:[~2017-02-24 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24  8:16 [PATCH 0/2] Tcsh update for core-updates Leo Famulari
2017-02-24  8:16 ` [PATCH 1/2] gnu: tcsh: Update to 6.20.00 Leo Famulari
2017-02-24  8:16 ` [PATCH 2/2] gnu: tcsh: Use modify-phases Leo Famulari
2017-02-24 10:46   ` Marius Bakke
2017-02-24  9:40 ` [PATCH 0/2] Tcsh update for core-updates ng0
2017-02-24 16:55   ` Leo Famulari
2017-02-24 17:28     ` ng0 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170224172835.ksfnvbcqw5rqprwa@wasp \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).