Hi Siddesh,
We recently encountered a case in our glibc patchwork instance on
sourceware, where a patch was dropped because it had x-unknown
charset. I used the following patch to fix this in our instance. The
fix I used was to fall back on a set of encodings (instead of just
utf-8) when the
Hi Brian,
When merging upstream work related to other projects into your own
project repository, you probably don't want to check for (and try to
update) the status on every change-set in the merge. So add a list of
references (branches, tags, commits, etc.) whose commits should be
ignored in
Looking at my own patch again...
On Thu, Jul 3, 2014 at 5:49 PM, Jeremy Kerr j...@ozlabs.org wrote:
...
Signed-off-by: Brian Norris computersforpe...@gmail.com
---
tools/post-receive.hook | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tools/post-receive.hook
Hi Yann,
On 2014-07-01 20:14 +0200, Yann E. MORIN spake thusly:
Here is an attempt to change the format of ~/.pwclientrc so it is easier
to manage such scatered-around projects.
Does this new series address your concerns about the previous one?
Do you have additional comments?
This looks
On second (third?) thought...
On Thu, Jul 3, 2014 at 5:56 PM, Brian Norris
computersforpe...@gmail.com wrote:
On Thu, Jul 3, 2014 at 5:49 PM, Jeremy Kerr j...@ozlabs.org wrote:
...
@@ -39,7 +45,8 @@ set_patch_state()
update_patches()
{
local cnt; cnt=0
- for rev in $(git rev-list
