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
--
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
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
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
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
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
6 matches
Mail list logo