Re: [tm-dev] TM on Github

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [tm-dev] TM on Github

From: David Dykstal <david_dykstal@xxxxxxxxxx>
Date: Fri, 15 Mar 2013 08:00:58 -0500
Delivered-to: tm-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/tm-dev>
List-help: <mailto:tm-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/tm-dev>, <mailto:tm-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/tm-dev>, <mailto:tm-dev-request@eclipse.org?subject=unsubscribe>

Martin --

I assume we could accomplish this synchronization with a small script that just pushes the updates to a GitHub clone and that there is no extra doctoring needed?

I'm not sure I completely understand the motivation here. This would be an exact replica of the TM repository and yet somehow linked to other forks to facilitate merging of interesting patches? What are the IP review implications? I'm having trouble visualizing the workflow.

-- David Dykstal, Architect - Rational Developer for Power Systems

References:
- [tm-dev] TM on Github
  - From: Oberhuber, Martin
- Re: [tm-dev] TM on Github
  - From: Anna Dushistova
- Re: [tm-dev] TM on Github
  - From: Oberhuber, Martin

Prev by Date: [tm-dev] Generating the Eclipse-Source|References Header
Next by Date: Re: [tm-dev] Generating the Eclipse-Source|References Header
Previous by thread: Re: [tm-dev] TM on Github
Next by thread: [tm-dev] Generating the Eclipse-Source|References Header
Index(es):
- Date
- Thread

Breadcrumbs