From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 30328@debbugs.gnu.org
Subject: [bug#30328] [PATCH] gnu: Add emacs-browse-at-remote-gnu.
Date: Wed, 07 Feb 2018 22:41:53 +0100 [thread overview]
Message-ID: <87eflwzdcu.fsf@gnu.org> (raw)
In-Reply-To: <877eroycvj.fsf@gmail.com> (Oleg Pykhalov's message of "Wed, 07 Feb 2018 19:37:36 +0300")
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
> >> > What about simply adding the patch to ‘emacs-browse-at-remote’ if
> >> > it’s committed upstream way?
> >>
> >> I'm sorry, what do you mean by “committed upstream way”?
> >
> > I mean that the patch for Savannah support is already in the repository
> > of ‘browse-at-remote’, isn’t it?
>
> Technically it is there.
Good.
> > Which is to say that the next version of ‘browse-at-remote’ will
> > have that functionality.
> >
> > I don’t know, won’t the next ‘browse-at-remote’ include it?
>
> I hope so, but I cannot answer for them (upstream).
Well if it’s already in their repo, let’s assume it’ll be in the next
version.
> > The output of ‘guix lint’ seems to be messy, too.
>
> Do you mean “filled”? Sorry for that.
Several lines appear to overlap.
> So, what will our strategy be? Stay close to upstream by making a new
> package with patch or patching the original package?
Patch the ‘emacs-browse-at-remote’ package, I’d say.
Sounds good?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-02-07 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 21:44 [bug#30328] [PATCH] gnu: Add emacs-browse-at-remote-gnu Oleg Pykhalov
2018-02-06 15:26 ` Ludovic Courtès
2018-02-06 16:47 ` Oleg Pykhalov
2018-02-07 9:18 ` Ludovic Courtès
2018-02-07 16:37 ` Oleg Pykhalov
2018-02-07 21:41 ` Ludovic Courtès [this message]
2018-02-09 19:26 ` Oleg Pykhalov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eflwzdcu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30328@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.