Re: Tracking vendor release with Git

2013-06-12 Thread Carsten Fuchs
Hi Yann, Am 2013-06-11 19:06, schrieb Yann Droneaud: I'm trying to setup a workflow to track vendor releases (upstream). Each new release are provided as an archive of source code, data, documentation, etc. For each vendor releases, fixes need to be applied before making them available to

Tracking vendor release with Git

2013-06-11 Thread Yann Droneaud
-- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Tracking vendor release with Git

2013-06-11 Thread Yann Droneaud
Hi, I'm trying to setup a workflow to track vendor releases (upstream). Each new release are provided as an archive of source code, data, documentation, etc. For each vendor releases, fixes need to be applied before making them available to users (downstream). Seems to be a rather common use

Re: Tracking vendor release with Git

2013-06-11 Thread Greg Troxel
I'm trying to setup a workflow to track vendor releases (upstream). Each new release are provided as an archive of source code, data, documentation, etc. I've been doing more or less this. A few comments: I suggest that you not view CRLF-LF as a patch. I would do EOL hygiene as a

Re: Tracking vendor release with Git

2013-06-11 Thread Johannes Sixt
Am 11.06.2013 19:06, schrieb Yann Droneaud: Hi, I'm trying to setup a workflow to track vendor releases (upstream). Each new release are provided as an archive of source code, data, documentation, etc. For each vendor releases, fixes need to be applied before making them available to

Re: Tracking vendor release with Git

2013-06-11 Thread Philip Oakley
From: Yann Droneaud ydrone...@opteya.com Sent: Tuesday, June 11, 2013 6:06 PM Hi, I'm trying to setup a workflow to track vendor releases (upstream). Each new release are provided as an archive of source code, data, documentation, etc. For each vendor releases, fixes need to be applied before