On 22 March 2016 at 06:14, Jim Jagielski wrote:
> Well, it looks like the format has been changing... so I
> can see concerns.
>
> But really, I'm not sure why it needs to be so
> "standardized" esp when it's mucking around with
> stuff it has no reason to. It's adding a line, so
> I don't see the
On Mon, Mar 21, 2016 at 4:51 PM, Jim Jagielski wrote:
> Just tried:
>
> % vi README.md
> % git commit -a
> [master a4f772a] test
> 1 file changed, 1 insertion(+), 1 deletion(-)
> % git push
> Username for 'https://git-dual.apache.org': jim
> Password for 'https://j...@git-dual.apache.org':
> C
Just tried:
% vi README.md
% git commit -a
[master a4f772a] test
1 file changed, 1 insertion(+), 1 deletion(-)
% git push
Username for 'https://git-dual.apache.org': jim
Password for 'https://j...@git-dual.apache.org':
Counting objects: 3, done.
Delta compression using up to 24 threads.
Compre
On Mon, Mar 21, 2016 at 4:38 PM, sebb wrote:
> On 21 March 2016 at 20:32, Jim Jagielski wrote:
>> I do, but I'm still unclear on dealing w/ the GH workflow.
>>
>> Can I just do it via svn, or even *our* git and not deal
>> w/ GH at all?
You can do it entirely using *our* git and not deal with GH
On 21 March 2016 at 20:32, Jim Jagielski wrote:
> I do, but I'm still unclear on dealing w/ the GH workflow.
>
> Can I just do it via svn, or even *our* git and not deal
> w/ GH at all?
You can certainly just work on a clone of our Git; no need to use
GitHub (once you are set up correctly).
>> O
I do, but I'm still unclear on dealing w/ the GH workflow.
Can I just do it via svn, or even *our* git and not deal
w/ GH at all?
> On Mar 21, 2016, at 4:19 PM, Sam Ruby wrote:
>
> On Mon, Mar 21, 2016 at 3:14 PM, Jim Jagielski wrote:
>> Well, it looks like the format has been changing... so I
On Mon, Mar 21, 2016 at 3:14 PM, Jim Jagielski wrote:
> Well, it looks like the format has been changing... so I
> can see concerns.
>
> But really, I'm not sure why it needs to be so
> "standardized" esp when it's mucking around with
> stuff it has no reason to. It's adding a line, so
> I don't s
Well, it looks like the format has been changing... so I
can see concerns.
But really, I'm not sure why it needs to be so
"standardized" esp when it's mucking around with
stuff it has no reason to. It's adding a line, so
I don't see the reason why it has to "recreate" the
file in the 1st place. Ei
I think having a proxy web interface continues to be a good idea; but we
need to come to a common understanding of the data format. Too late for
this meeting, but I'm inclined to change to a JSON format for future
meetings.
Here's the relevant lines:
https://github.com/apache/whimsy/blob/c53
