unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: 28210@debbugs.gnu.org
Cc: alezost@gmail.com
Subject: [bug#28210] closed (Re: [bug#28210] [PATCH] gnu: Add emacs-sr-speedbar.)
Date: Thu, 28 Sep 2017 19:11:36 +0300	[thread overview]
Message-ID: <8760c2sszr.fsf@gmail.com> (raw)
In-Reply-To: <handler.28210.D28210.150661371217571.notifdone@debbugs.gnu.org> (GNU bug Tracking System's message of "Thu, 28 Sep 2017 15:49:01 +0000")

help-debbugs@gnu.org (GNU bug Tracking System) writes:

> Please make sure your patches can be applied to the master branch of the
> guix git repo.  I often have problems with your patches (git complains
> with: "Patch format detection failed", so I have to make some manual
> interventions).  I don't know, maybe you make your patches on an
> outdated git checkout or in a separate branch that differs from master a
> lot.  Just a friendly note :-)

Hm.  I switched to rebasing onto origin/master some time ago.  I have 2
commits from myself on top of origin/master.

Before sending a patch, I rearrange them with rebasing, so patch commit
be on top of origin/master.  Probably I forgot to do this last time,
sorry.

I probably need to script a test for merging a patch into origin/master
before sending.

      parent reply	other threads:[~2017-09-28 16:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 19:55 [bug#28210] [PATCH] gnu: Add emacs-sr-speedbar Oleg Pykhalov
2017-08-23 20:34 ` Jonathan Brielmaier
2017-08-24 13:41   ` Oleg Pykhalov
2017-08-31 12:50     ` Ludovic Courtès
2017-09-04 19:39       ` Alex Kost
2017-09-17  9:03         ` Oleg Pykhalov
2017-09-18 17:42           ` Alex Kost
2017-09-23  2:18             ` Oleg Pykhalov
2017-09-28 15:48               ` bug#28210: " Alex Kost
     [not found] ` <handler.28210.D28210.150661371217571.notifdone@debbugs.gnu.org>
2017-09-28 16:11   ` Oleg Pykhalov [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=8760c2sszr.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=28210@debbugs.gnu.org \
    --cc=alezost@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 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).