[fossil-users] 2nd Call For Papers - 24th Annual Tcl/Tk Conference (Tcl'2017)

[akupries]

Hello Fossil Users, fyi ...

24th Annual Tcl/Tk Conference (Tcl'2017)
http://www.tcl.tk/community/tcl2017/

October 16 - 20, 2017
Crowne Plaza Houston River Oaks
2712 Southwest Freeway, 77098
Houston, Texas, USA

Important Dates:

Abstracts and proposals due   August 21, 2017
Notification to authors   August 28, 2017
WIP and BOF reservations open July 24, 2017
Author materials due  September 25, 2017
Tutorials Start   October 16, 2017
Conference starts October 18, 2017

Email Contact:tclconfere...@googlegroups.com

Submission of Summaries

Tcl/Tk 2017 will be held in Houston, Texas, USA from October 16, 2017 to 
October 20, 2017.

The program committee is asking for papers and presentation proposals
from anyone using or developing with Tcl/Tk (and extensions). Past
conferences have seen submissions covering a wide variety of topics
including:

* Scientific and engineering applications
* Industrial controls
* Distributed applications and Network Managment
* Object oriented extensions to Tcl/Tk
* New widgets for Tk
* Simulation and application steering with Tcl/Tk
* Tcl/Tk-centric operating environments
* Tcl/Tk on small and embedded devices
* Medical applications and visualization
* Use of different programming paradigms in Tcl/Tk and proposals for new
  directions.
* New areas of exploration for the Tcl/Tk language

Submissions should consist of an abstract of about 100 words and a
summary of not more than two pages, and should be sent as plain text
to tclconfere...@googlegroups.com no later than August 21, 2017. Authors of 
accepted
abstracts will have until September 25, 2017 to submit their final
paper for the inclusion in the conference proceedings. The proceedings
will be made available on digital media, so extra materials such as
presentation slides, code examples, code for extensions etc. are
encouraged.

Printed proceedings will be produced as an on-demand book at lulu.com

The authors will have 30 minutes to present their paper at
the conference.

The program committee will review and evaluate papers according to the
following criteria:

* Quantity and quality of novel content
* Relevance and interest to the Tcl/Tk community
* Suitability of content for presentation at the conference

Proposals may report on commercial or non-commercial systems, but
those with only blatant marketing content will not be accepted.

Application and experience papers need to strike a balance between
background on the application domain and the relevance of Tcl/Tk to
the application. Application and experience papers should clearly
explain how the application or experience illustrates a novel use of
Tcl/Tk, and what lessons the Tcl/Tk community can derive from the
application or experience to apply to their own development efforts.

Papers accompanied by non-disclosure agreements will be returned to
the author(s) unread. All submissions are held in the highest
confidentiality prior to publication in the Proceedings, both as a
matter of policy and in accord with the U. S. Copyright Act of 1976.

The primary author for each accepted paper will receive registration
to the Technical Sessions portion of the conference at a reduced rate.

Other Forms of Participation

The program committee also welcomes proposals for panel discussions of
up to 90 minutes. Proposals should include a list of confirmed
panelists, a title and format, and a panel description with position
statements from each panelist. Panels should have no more than four
speakers, including the panel moderator, and should allow time for
substantial interaction with attendees. Panels are not presentations
of related research papers.

Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather
sessions (BOFs) are available on a first-come, first-served basis
starting in July 24, 2017. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in July 24, 2017. Some WIP and BOF time slots will be held open
for on-site reservation. All attendees with an interesting work in
progress should consider reserving a WIP slot.

Registration Information

More information on the conference is available the conference Web
site (http://www.tcl.tk/community/tcl2017/) and will be published on
various Tcl/Tk-related information channels.

To keep in touch with news regarding the conference and Tcl events in
general, subscribe to the tcl-announce list. See:
http://code.activestate.com/lists/tcl-announce to subscribe to the
tcl-announce mailing list.


Conference Committee

   * Alexandre Ferrieux
   * Andreas KupriesSUSE
   * Arjen Markus   Deltares
   * Brian Griffin  Mentor Graphics - A Siemens Business
   * Clif Flynt Noumena Corp
   * Gerald Lester  KnG Consulting LLC
   * Joe Mistachkin Mistachkin Systems
   * Ronald Fox CAEN Technologies
NSCL @ Michigan State University
   * Steve Landers  

Re: [fossil-users] Is it possible to merge repository's?

[David Mason]

You can have a working directory for one repository nested inside a folder in a 
working directory of another repository.  See the —nested option for `fossil 
open`.

I use this *extensively*. It’s very convenient. But it may not be quite what 
you want because you do have to commit separately for each repo.

../Dave

On May 31, 2017, 12:37 PM -0400, The Tick , wrote:
> The reason I had is because I started a subproject and, after a couple
> weeks, realized that it would be more convenient to have its repository
> merged into my main project as a sub-directory. I thought this might be
> an existing feature somehow.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Is it possible to merge repository's?

[The Tick]

On 5/31/2017 10:57 AM, Ron W wrote:

On Tue, May 30, 2017 at 8:00 AM,
> wrote:

Date: Mon, 29 May 2017 22:35:31 -0500
From: The Tick >
Subject: Re: [fossil-users] Is it possible to merge repository's?

On 5/29/2017 10:30 PM, Andy Bradford wrote:
> Thus said Stephan Beal on Tue, 30 May 2017 02:57:38 +0200:
>
>> However, there is  _hypothetically_ a way to completely  merge 2
repos
>> into one while keeping all commits, but i'm not at all certain if
this
>> would work...
>
> I think it actually will work for some definition of ``work''.
I've done
> it before.
>
> But... it depends on what one expects out of it.
>
> There will  be 2 separate  and independent timelines  once
reconstructed
> and there  will not be a  relationship between artifacts except
for the
> fact that they all live in the same Fossil file.
>

 From this I gather that there would be no way to connect the imported
repository onto the main trunk. That was not what I was hoping for.


What is your objective?

Once you have both time lines in one repository, you can then fetch
files from both into a single checkout and start making checkins  that
affect both timelines, therefore, effectively merging the timelines at
that checkin.

To get the "combined" checkout, I think you would have to "fossil
checkout uuidLatestA", then make a trivial change to all the files, then
"fossil update uuidLatestB".

At this point a commit would affect both timelines.

Though, as Stephan mentioned, you might need to do a reparent command to
insure that both uuidLatestA and uuidLatestB are parents of this new commit.



Thanks for the suggestions.

The reason I had is because I started a subproject and, after a couple 
weeks, realized that it would be more convenient to have its repository 
merged into my main project as a sub-directory. I thought this might be 
an existing feature somehow.


As I have just begun using fossil in the past month or so, the 
suggestions here are pretty much over my head and I don't feel 
comfortable enough with fossil to begin experimenting at this depth.



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Is it possible to merge repository's?

[Ron W]

On Tue, May 30, 2017 at 8:00 AM, 
wrote:
>
> Date: Mon, 29 May 2017 22:35:31 -0500
> From: The Tick 
> Subject: Re: [fossil-users] Is it possible to merge repository's?
>
> On 5/29/2017 10:30 PM, Andy Bradford wrote:
> > Thus said Stephan Beal on Tue, 30 May 2017 02:57:38 +0200:
> >
> >> However, there is  _hypothetically_ a way to completely  merge 2 repos
> >> into one while keeping all commits, but i'm not at all certain if this
> >> would work...
> >
> > I think it actually will work for some definition of ``work''. I've done
> > it before.
> >
> > But... it depends on what one expects out of it.
> >
> > There will  be 2 separate  and independent timelines  once reconstructed
> > and there  will not be a  relationship between artifacts except  for the
> > fact that they all live in the same Fossil file.
> >
>
>  From this I gather that there would be no way to connect the imported
> repository onto the main trunk. That was not what I was hoping for.
>

What is your objective?

Once you have both time lines in one repository, you can then fetch files
from both into a single checkout and start making checkins  that affect
both timelines, therefore, effectively merging the timelines at that
checkin.

To get the "combined" checkout, I think you would have to "fossil checkout
uuidLatestA", then make a trivial change to all the files, then "fossil
update uuidLatestB".

At this point a commit would affect both timelines.

Though, as Stephan mentioned, you might need to do a reparent command to
insure that both uuidLatestA and uuidLatestB are parents of this new commit.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users