From: Dennis Schridde <devurandom@gmx.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Multiple user questions
Date: Sat, 24 May 2008 11:13:54 +0200 [thread overview]
Message-ID: <200805241113.57848.devurandom@gmx.net> (raw)
In-Reply-To: <m3zlqg32w9.fsf@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1826 bytes --]
Thanks for your answers!
Am Samstag, 24. Mai 2008 03:30:43 schrieb Jakub Narebski:
> Dennis Schridde <devurandom@gmx.net> writes:
> > 2) Can I make format-patch include the full commit message, date, author,
> > stats in the patches? (To mimic what git-show would show me.)
> > Will this be sent via send-email, too?
>
> Errr... git-format-patch output _does_ include full commit message,
> author, author date and diffstat.
For me only the first line of the commit message is printed in the subject,
all other lines are missing.
If I want a message to appear in the body at all, I need a special way to
format my commit messages: 1 line summary, 1 empty line, description.
Only the description is then shown in the email.
This seems inconvenient, especially for smaller changes.
Further, attachments do not at all contain any information like that.
See the attached example.
> > 4) Can I make format-patch output one deletion and one insertion for a
> > complete rewrite of a function, instead of multiple deletes/inserts?
>
> Try git-format-patch with -B option, or -B<num>.
I tried that already.
Whether I specified -B or not, it always gave the exact same output (says
diff).
The <num> parameter to -B is not mentioned or explained in the manpages.
5) fsck --full --lost-found shows me a lot of "dangling commit". I would like
to clean them up. prune did only remove "dangling tree" and blobs.
(Reason: Last time I droped a stash accidently, I was able to find it in that
list. I will not be able to do this again if it continues to grow at that
rate.)
How can I do that?
Further fsck --full --unreachable also shows a lot of unreachable things
(commits, trees, blobs). Can that be cleaned up as well?
Greetings,
Dennis
Again: Please CC me, as I am not subscribed.
[-- Attachment #1.2: 5b7f87a087d7372b04fd81202191a3d8cb818bab.diff --]
[-- Type: text/x-diff, Size: 1190 bytes --]
diff --git a/src/projectile.c b/src/projectile.c
index 1389d4c..f9ae99a 100644
--- a/src/projectile.c
+++ b/src/projectile.c
@@ -640,8 +640,8 @@ static void proj_InFlightDirectFunc( PROJECTILE *psProj )
/* we want a delay between Las-Sats firing and actually hitting in multiPlayer
magic number but that's how long the audio countdown message lasts! */
const unsigned int LAS_SAT_DELAY = 8;
- unsigned int timeSoFar;
- unsigned int distancePercent; /* How far we are 0..100 */
+ int timeSoFar;
+ int distancePercent; /* How far we are 0..100 */
float distanceRatio; /* How far we are, 1.0==at target */
float distanceExtensionFactor; /* Extended lifespan */
Vector3i move;
@@ -909,8 +909,8 @@ static void proj_InFlightIndirectFunc( PROJECTILE *psProj )
- Some optimisations by leaving out tests which are never true (homing, AA, counter-missile, lassat)
*/
- unsigned int timeSoFar;
- unsigned int distancePercent; /* How far we are 0..100 */
+ int timeSoFar;
+ int distancePercent; /* How far we are 0..100 */
float distanceRatio; /* How far we are, 1.0==at target */
float distanceExtensionFactor; /* Extended lifespan */
Vector3i move;
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-05-24 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 11:27 Multiple user questions Dennis Schridde
2008-05-23 11:37 ` Dennis Schridde
2008-05-24 1:30 ` Jakub Narebski
2008-05-24 9:13 ` Dennis Schridde [this message]
2008-05-24 12:33 ` Jakub Narebski
2008-05-25 8:49 ` Dennis Schridde
2008-05-27 8:24 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2008-06-06 20:47 Dennis Schridde
2008-06-06 21:19 ` Brandon Casey
2008-06-06 22:15 ` Dennis Schridde
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=200805241113.57848.devurandom@gmx.net \
--to=devurandom@gmx.net \
--cc=git@vger.kernel.org \
--cc=jnareb@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.
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 NNTP newsgroup(s).