Re: [translations] italian website PATCH |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: Federico Bruni <fedelogy@xxxxxxxxx>
- Subject: Re: [translations] italian website PATCH
- From: Francisco Vila <paconet.org@xxxxxxxxx>
- Date: Fri, 18 Jun 2010 10:38:52 +0200
- Cc: translations@xxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0CkieMH2G8wfRtFoULfq3LyGbvQAff41ZrdG1GoyPCQ=; b=p/34rrFlYWHlnYgXCrhUdwlG4XUBA6FSm+T45HgX6oQPaK+8xHCXx3RDzTwKUxhXRw 7ZYEu4iXLh7kTaEgMW/7xYiweEPxjbgw1tNqP+Wu7u6oJTzFZHBamN9kseLgrCTF5Go7 yhLa5msqlwaRLq+7RdshcSt+Xpq5726dPO6B0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=k5dVWElUOS3svE63WuN1e3WHil6Yby3oLA3n3xrbKY7K3le30jZJGWGxRnDxnFizmB yQVgQo8fvcvRbESYmcxoN5lW7aoWtD5I77PirzFxUX/sxV3JpRvTWZAXMJRBGxDKRl5B r8kpYL6wbJBXEKlX7T/MWTsOBsG0NmNRYUhHs=
2010/6/18 Federico Bruni <fedelogy@xxxxxxxxx>:
> First, rewinding head to replay your work on top of it...
> Applying: Web-it: add italian translation
> Using index info to reconstruct a base tree...
> <stdin>:2107: trailing whitespace.
> delle funzionalità tipografiche più avanzate, come la ripartizione di
> travature
Remove the trailing space og the line 2107.
> <stdin>:3404: trailing whitespace.
> Quasi tutte le funzionalità di formattazione usate internamente sono
Same.
> <stdin>:365: new blank line at EOF.
> +
Go to line 365 of the patch; the file diff that starts at this point
adds a blank line at the end of the file (many lines downwards).
> <stdin>:1265: new blank line at EOF.
> +
Same.
Alternatively to the git mess you could eventually enter, you could do
the following.
-- Save your modified files the way you think they should be, with safe names.
-- Git reset --hard to a revision just before your changes.
-- Git pull to update your tree
-- Copy your modified files back to their original names
-- Commit these differences
-- Make a patch from this.
When I don't understand what's happening (more often than not), this
method usually works.
The problem would be: if someone modified any lines after your
changes, these modifications would be lost. That's what git was
invented for :-)
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com