From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catonano Subject: Re: workflow Date: Thu, 4 Jan 2018 12:30:19 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114bb98e30d98f0561f1a884" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56487) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eX3j5-0007m9-OK for guix-devel@gnu.org; Thu, 04 Jan 2018 06:30:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eX3j3-0004ZC-RP for guix-devel@gnu.org; Thu, 04 Jan 2018 06:30:23 -0500 Received: from mail-yb0-x22d.google.com ([2607:f8b0:4002:c09::22d]:42474) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eX3j3-0004YL-6n for guix-devel@gnu.org; Thu, 04 Jan 2018 06:30:21 -0500 Received: by mail-yb0-x22d.google.com with SMTP id q3so486301ybg.9 for ; Thu, 04 Jan 2018 03:30:21 -0800 (PST) In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Hartmut Goebel Cc: guix-devel --001a114bb98e30d98f0561f1a884 Content-Type: text/plain; charset="UTF-8" 2018-01-04 11:13 GMT+01:00 Hartmut Goebel : > Am 04.01.2018 um 10:46 schrieb Catonano: > > This is a little bit annoying, as I can't rebase my branch on master > > in order to edit the commit message without dealing with those too > > (stashing or checking them out back to where they were) > > Try this: > > git checkout po > So the best practice is to deal with them ;-) Ok, at least this happens only the first time and thhen no more Thanks ! --001a114bb98e30d98f0561f1a884 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2018-01-04 11:13 GMT+01:00 Hartmut Goebel <h.g= oebel@crazy-compilers.com>:
Am = 04.01.2018 um 10:46 sc= hrieb Catonano:
> This is a little bit annoying, as I can't rebase my branch on mast= er
> in order to edit the commit message without dealing with those too
> (stashing or checking them out back to where they were)

Try this:

git checkout po

So the best practice is= to deal with them ;-)

Ok, at least this happens only th= e first time and thhen no more

Thanks !
--001a114bb98e30d98f0561f1a884--