Does the e-mail
[email protected]
exist ?
Do we have another list now ? I've got the bounce below...
do we have a separate list for git troubles ? Why ? Isn't it better to
discuss git-related issues on lyx-devel ? After all, all developers are
supposed to adapt to the new system, aren't they ?
T.
-------- Messaggio originale --------
Oggetto: Delivery Status Notification (Failure)
Data: Mon, 19 Mar 2012 01:45:22 +0000
Mittente: Mail Delivery Subsystem <[email protected]>
A: [email protected]
Hello [email protected],
We're writing to let you know that the group you tried to contact (git-users)
may not exist, or you may not have permission to post messages to the group. A
few more details on why you weren't able to post:
* You might have spelled or formatted the group name incorrectly.
* The owner of the group may have removed this group.
* You may need to join the group before receiving permission to post.
* This group may not be open to posting.
If you have questions related to this or any other Google Group, visit the Help
Center at
http://www.google.com/support/a/lyx.org/bin/static.py?hl=en_US&page=groups.cs.
Thanks,
lyx.org admins
----- Original message -----
Received: by 10.180.95.74 with SMTP id di10mr25271927wib.1.1332121522449;
Sun, 18 Mar 2012 18:45:22 -0700 (PDT)
Received: by 10.180.95.74 with SMTP id di10mr25271926wib.1.1332121522432;
Sun, 18 Mar 2012 18:45:22 -0700 (PDT)
Return-Path:<[email protected]>
Received: from mail-we0-f178.google.com (mail-we0-f178.google.com
[74.125.82.178])
by mx.google.com with ESMTPS id m5si7912813wiw.25.2012.03.18.18.45.22
(version=TLSv1/SSLv3 cipher=OTHER);
Sun, 18 Mar 2012 18:45:22 -0700 (PDT)
Received-SPF: neutral (google.com: 74.125.82.178 is neither permitted nor
denied by best guess record for domain of [email protected])
client-ip=74.125.82.178;
Authentication-Results: mx.google.com; spf=neutral (google.com: 74.125.82.178
is neither permitted nor denied by best guess record for domain of
[email protected]) [email protected]
Received: by wera13 with SMTP id a13so7326107wer.37
for<[email protected]>; Sun, 18 Mar 2012 18:45:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=message-id:date:from:user-agent:mime-version:to:cc:subject
:references:in-reply-to:content-type:content-transfer-encoding
:x-gm-message-state;
bh=pEhffGdteeUHgeQYNqX9f6RQdi1/T6nqdNY3+uTtZkM=;
b=Q+z2FyLcoUViMiPsXCOD4RYxeWuSAL8X7iJCGY6Vu/A1UwB4L6xVa4POXvax/TaTH1
QtN2Z3Gl7PHb0pl8mwnGTkhrD+2CfrIE6nQDxnaZ2/NI/UED1fUJMswXw/tP2RJwDxGw
MRBrxFpgqwVBry7rb4BFTI6EyXq/Yciz201rGyvWpXFZPO8ZMrQI8AxUnRlKyAQs0GLi
xibGLJTq0nuNt+f5mci1icmlH7/++vvmN08B78iQWo6PFVmyx6TEGZP3WTF61wX/9dye
xrs+tiflQsj4/cu0qPMo1cEkZmbnc7GHpqrGkodROWmQMsjnC2Hma5X0ppH0EAgbPxTK
45Zg==
Received: by 10.216.138.17 with SMTP id z17mr6136980wei.18.1332121521974;
Sun, 18 Mar 2012 18:45:21 -0700 (PDT)
Return-Path:<[email protected]>
Received: from [109.125.27.87] ([109.125.27.87])
by mx.google.com with ESMTPS id k6sm21607982wie.9.2012.03.18.18.45.20
(version=SSLv3 cipher=OTHER);
Sun, 18 Mar 2012 18:45:21 -0700 (PDT)
Message-ID:<[email protected]>
Date: Mon, 19 Mar 2012 01:45:16 +0000
From: Tommaso Cucinotta<[email protected]>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216
Thunderbird/10.0.2
MIME-Version: 1.0
To: =?UTF-8?B?VXdlIFN0w7Zocg==?=<[email protected]>
CC: [email protected], LyX-Devel<[email protected]>
Subject: Re: [patch] How can I show a patch to the list using Git?
References:<[email protected]>
In-Reply-To:<[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Gm-Message-State:
ALoCoQkTDwhBjuDV1wND9o9KXdnNBjPhXO/XWgr7k5sPgUbKebrUceKNz7rjrAVAbYeT2rsvE7Lp
Il 19/03/2012 01:02, Uwe Stöhr ha scritto:
As suggested I branched the Git master to develop a new feature. Now I
think this feature is now ready and I want to show it on the list but
how can I do that?
I tried to generate a patch from my branch but I only get a success
message and no file is generated.
guess
git show commit..commit> cool.patch
or, if u remember that your patch is, let's say, 2 commits, something like:
git show HEAD~2..HEAD> cool.patch
(assuming your committed patches sit on top of everything else, in
your local branch)
Should you have pulled after committing your patches locally, then you
might have others' patches on top of yours, so you should pick
selectively the patches by their ID. Alternatively, try a rebase (i.e.,
an update of the patchset to the latest remote repo), but that's among
the things I cannot do :-)
If, instead, your patch is not committed not even in your local branch,
then the usual:
git diff> cool.patch
I can also not push it to somewhere as i don't know where.
if your branch is local on your machine, one of the above, and send to
the list. If you add a remote branch on the main repo, or on your own
separate repo, then you may push there and ask on the list to people to
fetch the patch from there, but this is the domain of "--reset --hard",
or "cherry-pick", which are things I don't know how to use.
Hope this helps,
T.