<div dir="ltr">Hi Dscho,<div><br></div><div><div>> So by removing the topic branches, we also removed the documentation</div><div>> from what source we used to build certain revisions of our bio-formats</div><div>> submodule.</div>
</div><div><br></div><div>If you think this is a problem, I am fine with reinstating the branches. I still have the local branch pointers and can easily push them back if that's what you want.</div><div><br></div><div>
Personally I just thought the benefits of simplification outweighed preserving such (minor) history. My thinking is that many more people will be looking at the list of repos in those namespaces and potentially wondering why we keep a fork of the project, versus the likely extremely small number (potentially zero) of developers digging through the git history and cross-checking against the given links, etc.</div>
<div><br></div><div>Regards,</div><div>Curtis</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 18, 2013 at 11:53 AM, Johannes Schindelin <span dir="ltr"><<a href="mailto:Johannes.Schindelin@gmx.de" target="_blank">Johannes.Schindelin@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">HI Curtis,<br>
<div><div class="h5"><br>
On Fri, 18 Oct 2013, Curtis Rueden wrote:<br>
<br>
> The Fiji and ImageJ namespaces on GitHub each have a fork of<br>
> openmicroscopy/bioformats. This was done so that we could have a special<br>
> branch ("fiji" in the case of fiji, and "imagej" in the case of imagej)<br>
> that point to the version of Bio-Formats artifacts currently distributed on<br>
> the Fiji and ImageJ update sites, respectively.<br>
><br>
> However, those branches are now obsolete: starting with 4.4.9 we always<br>
> ship the stable release version of Bio-Formats with Fiji. And we do not<br>
> ship any Bio-Formats artifacts at all with ImageJ2. The Bio-Formats page on<br>
> the Fiji wiki page also no longer references these GitHub forks at all.<br>
><br>
> Users who want the latest and greatest bugfixes can now enable the<br>
> "Bio-Formats daily builds" update site as described at<br>
> <a href="http://fiji.sc/Bio-Formats#Daily_builds" target="_blank">http://fiji.sc/Bio-Formats#Daily_builds</a>.<br>
><br>
> Hence, I already deleted the "fiji" and "imagej" branches from those source<br>
> forks. But I would actually like to completely remove the forks themselves,<br>
> to avoid confusion. The fiji fork has no topic branches and I believe is<br>
> safe to be deleted. The imagej fork has one topic branch called<br>
> "performance" created by dscho. But dscho also has his own project fork in<br>
> his namespace too. So Dscho: are you OK with migrating that topic branch<br>
> there instead?<br>
><br>
> Any objections to this plan?<br>
<br>
</div></div>The only objection I have is that we referenced some of those commits in<br>
fiji.git's history... So by removing the topic branches, we also removed<br>
the documentation from what source we used to build certain revisions of<br>
our bio-formats submodule.<br>
<br>
Not a big thing, though. I can easily hold those things in my personal<br>
fork.<br>
<br>
Ciao,<br>
Dscho<br>
</blockquote></div><br></div>